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

 

[1alien1]

ok i think i understand everything and thank you very much

 

[1alien1]

GW made that the combo for accessing the menu with the last version. It used to just be L before. You could use ReiNAND since it boots EmuNAND by default. Or you could hold L to boot EmuNAND with Luma. Either will work. When GW formats EmuNAND, it clones your SysNAND to it. So, any tickets on SysNAND will get transferred.

i just tried to downgrade in reinand and then this shows up what to do?

EDIT: it seems that the system settings shows rei 11.2 for me. so maybe it worked nontheless? strange is: after formating i started system nand. changed color to black (theme). then went into emunand, and it was black. now after downgrade my emunand is still black theme and sysnand is white again? are they not linked anymore? how can i check if nands are linked?
EDIT: seems like sysnand doesnt save my theme color anymore, after power off and on again ..
EDIT: gw emunand does not load anymore. i think something screwed up bigtime . loading the old sd card, everything seems to work as before. theme colors will save. gw emunand works..

 

[Kazuma77]

i just tried to downgrade in reinand and then this shows up what to do?

EDIT: it seems that the system settings shows rei 11.2 for me. so maybe it worked nontheless? strange is: after formating i started system nand. changed color to black (theme). then went into emunand, and it was black. now after downgrade my emunand is still black theme and sysnand is white again? are they not linked anymore? how can i check if nands are linked?
EDIT: seems like sysnand doesnt save my theme color anymore, after power off and on again ..
EDIT: gw emunand does not load anymore. i think something screwed up bigtime . loading the old sd card, everything seems to work as before. theme colors will save. gw emunand works..

Looks like one of the CIAs may have got corrupted or something. You could clone SysNAND to EmuNAND and try again (I'd recopy the CIAs over). Or just backup the EmuNAND on the old card, then copy it to the new one and restore it.

 

[1alien1]

Looks like one of the CIAs may have got corrupted or something. You could clone SysNAND to EmuNAND and try again (I'd recopy the CIAs over). Or just backup the EmuNAND on the old card, then copy it to the new one and restore it.

well i just started from scratch again, new sd card format emunand, clean sd. then i went into the systemmenue, and as before, the colors will always revert to white. changing, power off and power on will reset the theme color? what am i doing wrong? or is this normal?

EDIT: its the strangest thing. if i change theme color in emunand, it will stay after reboot. but sysnand always keeps reverting. this is making me insane...

 

[1alien1]

well i just started from scratch again, new sd card format emunand, clean sd. then i went into the systemmenue, and as before, the colors will always revert to white. changing, power off and power on will reset the theme color? what am i doing wrong? or is this normal?

EDIT: its the strangest thing. if i change theme color in emunand, it will stay after reboot. but sysnand always keeps reverting. this is making me insane...

and i got the same cia error while downgrading again as before, even though i redownloaded it fresh from nus. something is not working right ...
i will retest what happenes, if i transfer the sd card to the new one and not format emunand. i want to check if its working normally untill this point.

EDIT: its the same problem. when i just copy all the files from the old to the new sd card, and start the 3ds up. the theme is the white one and all changes do nothing. everything is saved, icon order, display brightness etc. only the theme reverts. i can also save the current black theme with arranged icons, and after reboot it will have the white one and i can load the black one again from the saved theme. but the standard just wont stay..any idea on what is going on? and also for the emunand im at a loss. i dont know exactly how to inject the bin into the emunand. my godmode launcher thin h as no setting for backup/inject nands. only the script for backup of your all in one file...

EDIT: the strangest thing, when i boot reinand without having emunand formated, it boots into reisysnand and there the old black theme is and changing the color will be saved upon reboot. whats happening? why is the luma sysnand acting up? should i reconfigure luma or something? if so, how can i do that?

 

[1alien1]

me again..:I
so i guess i have the solution to the problem. it seems the 3ds really has problems with 256gb cards. i have 3 original sandisk cards, all of which work properly. 2x 128gb and 1x 256gb. my original 128gb works well, i used it for the last week. i tried just copying over the content to the other 128gb card and everything works fine. as soon as i use the 256gb card, the home theme gets reset for some unknown reason. downgrading i didnt try with the other 128gb but i bet it would work and doesnt work with the 256gb. so i guess this is it huh?

 

[Kazuma77]

me again..:I
so i guess i have the solution to the problem. it seems the 3ds really has problems with 256gb cards. i have 3 original sandisk cards, all of which work properly. 2x 128gb and 1x 256gb. my original 128gb works well, i used it for the last week. i tried just copying over the content to the other 128gb card and everything works fine. as soon as i use the 256gb card, the home theme gets reset for some unknown reason. downgrading i didnt try with the other 128gb but i bet it would work and doesnt work with the 256gb. so i guess this is it huh?

Yeah, it sounds like that's what it must be. Well, the manual only says it takes SDHC. It doesn't really say anything about SDXC. We're lucky 128 works I guess. Though I guess it's possible GW messed up formatting the card. You could try with GM9 and see if that solves it.

To restore a NAND image manually, you can select the file, NAND image options, Mount image to drive, and then copy nand_minsize.bin (select it and hit Y) to the E: drive (go to the E: drive and hit Y again). Restore scripts were included in GodMode 1.4.2 (written by yours truly) and when I get R6 ready, it will include them. It's getting close. I just changed all B9S installers. They now let you pick between B9S and GM9 for your firm (and for that matter, any other .firm you want to add to the "boot9strap" folder, as long as it will verify, and you include an .sha file to check it). So, technically they're Sighax installers now. I'm going to add GM9 as a chainloader option and it will be ready for release I think (unless they manage to fix that display bug, but I'm about to give up on that).

 

[1alien1]

Yeah, it sounds like that's what it must be. Well, the manual only says it takes SDHC. It doesn't really say anything about SDXC. We're lucky 128 works I guess. Though I guess it's possible GW messed up formatting the card. You could try with GM9 and see if that solves it.

To restore a NAND image manually, you can select the file, NAND image options, Mount image to drive, and then copy nand_minsize.bin (select it and hit Y) to the E: drive (go to the E: drive and hit Y again). Restore scripts were included in GodMode 1.4.2 (written by yours truly) and when I get R6 ready, it will include them. It's getting close. I just changed all B9S installers. They now let you pick between B9S and GM9 for your firm (and for that matter, any other .firm you want to add to the "boot9strap" folder, as long as it will verify, and you include an .sha file to check it). So, technically they're Sighax installers now. I'm going to add GM9 as a chainloader option and it will be ready for release I think (unless they manage to fix that display bug, but I'm about to give up on that).

i dont think it will make a big difference, since the problem with the home theme arises even if i dont format emunand and only copy the files over. everything seemed to work (except the emunand downgrade which showed an error while showing it is 11.2 in the menue). but i dont want to realise after some time that other problems are also present so i will stick to the 128gb card i guess..

 

[1alien1]

hej, so i read a bit on the inet and all, and i tried something. formatting the sd with 64kbit cluster size instead of the recommended 32 solves the theme problem. but only if i dont format emunand with the gw menu, after that its the same old story, even if i format the partition in windows with 64kbit again. i guess that settles it and i cut the strings of gw...

 

[zebrone]

I've red your Tutorial. Gw runs very well.

I'm trying to upload luma from 7.0 to 8.0,but it gives me an error.
Is it cause i'm on A9LH?

Also, my fw is 9.0.0.20E NEW 3DSXL. How can i upload it to 11.20?

 

[Kazuma77]

I've red your Tutorial. Gw runs very well.

I'm trying to upload luma from 7.0 to 8.0,but it gives me an error.
Is it cause i'm on A9LH?

Also, my fw is 9.0.0.20E NEW 3DSXL. How can i upload it to 11.20?

That would be it. Luma 8.x only runs on Sighax. If you want to upgrade from A9LH, my InScripted AIO (that iso site, CFW Discussion section, I can't upload it here, because it would no longer be an AIO) has an extremely easy to use "A9LH to Sighax" installer. It also has a pre-made configuration for B9S that includes Gateway (it's hotkeyed to B by default, but I include GM9 scripts to change the hotkeys, so, you can make it whatever you want). Just copy the contents of the "N3DS" folder within the "B9S Configurations" folder over, then copy the contents of the "A9LH to B9S" folder within the "Installers" folder over, and place the card in your system. It will boot to GM9. Just hit home, more, scripts, select the "0 - Install Scripts" option. I would pick option 3. B9S tends to be all most people need, but having the "Switch Firms" script will allow you to checkout GM9 if you want to (though if you would rather not mess with it, just pick option 1).

Since you are on A9LH, you can safely update to 11.2 (this will remain true if you upgrade to Sighax). Just use the latest 3DNUS to grab 11.2 (type in 11.2.0-35E, and make sure the right hardware model is checked). Copy the CIAs to a folder named "updates" on the SD card, and use SysUpdater to update. I would heavily advise backing your card up, formatting EmuNAND, and restoring at some point. I realize it's time-consuming, but it really is the best way to go. Gateway makes you enter an extra key combo without an EmuNAND. Besides, if you do that, you can update SysNAND to 11.6 for use with Luma, and still be able to use Gateway on 11.2 via the EmuNAND (which it will load automatically if it finds one).

 

[zebrone]

That would be it. Luma 8.x only runs on Sighax. If you want to upgrade from A9LH, my InScripted AIO (that iso site, CFW Discussion section, I can't upload it here, because it would no longer be an AIO) has an extremely easy to use "A9LH to Sighax" installer. It also has a pre-made configuration for B9S that includes Gateway (it's hotkeyed to B by default, but I include GM9 scripts to change the hotkeys, so, you can make it whatever you want). Just copy the contents of the "N3DS" folder within the "B9S Configurations" folder over, then copy the contents of the "A9LH to B9S" folder within the "Installers" folder over, and place the card in your system. It will boot to GM9. Just hit home, more, scripts, select the "0 - Install Scripts" option. I would pick option 3. B9S tends to be all most people need, but having the "Switch Firms" script will allow you to checkout GM9 if you want to (though if you would rather not mess with it, just pick option 1).

Since you are on A9LH, you can safely update to 11.2 (this will remain true if you upgrade to Sighax). Just use the latest 3DNUS to grab 11.2 (type in 11.2.0-35E, and make sure the right hardware model is checked). Copy the CIAs to a folder named "updates" on the SD card, and use SysUpdater to update. I would heavily advise backing your card up, formatting EmuNAND, and restoring at some point. I realize it's time-consuming, but it really is the best way to go. Gateway makes you enter an extra key combo without an EmuNAND. Besides, if you do that, you can update SysNAND to 11.6 for use with Luma, and still be able to use Gateway on 11.2 via the EmuNAND (which it will load automatically if it finds one).

Thank you. I will try!!

 

[mijuu]

I can only get this to boot gw enand by disabling autoboot of emunand in luma options and holding down when powering on the console. How do I get this to autoboot into gw enand?

When autoboot emunand is enabled in the luma options, the L trigger and down has to held to boot into gw enand.

Any kind of auto boot enand in luma setting always boots the console into luma enand.

 

[Kazuma77]

I can only get this to boot gw enand by disabling autoboot of emunand in luma options and holding down when powering on the console. How do I get this to autoboot into gw enand?

When autoboot emunand is enabled in the luma options, the L trigger and down has to held to boot into gw enand.

Any kind of auto boot enand in luma setting always boots the console into luma enand.

EmuNAND is not proprietary. It contains zero patches. All CFWs (including Gateway mode) that support EmuNAND boot the same ones. CFWs do all of their patching in memory. There is no such thing as Luma EmuNAND or GW EmuNAND. There is just EmuNAND. Luma's chainloader is always going to boot into Luma by default (one of the primary reasons I don't use it). You have to use a real chainloader like BootCTR9 or CBM9 to get a choice of what CFW (or other app) boots by default. If you need an example of this, look up my InScripted AIO (that iso site, "CFW Discussion" section). Just copy the configuration over from "B9S Configurations" that matches your hardware. It boots Luma by default, Gateway on B, and GM9 is on left (among other things, a full list is included in the "ReadMe.txt" file). However, if you go into GM9, hit home, and select the Scripts menu, under "Default Payloads & Hotkeys" you will see an option to change the default payload. You can make it Gateway (or anything else).

If you do that, you no longer need Gateway on B. So you might want to reassign that hotkey. Luma's already hotkeyed to A as well, so unless you have a use for the "persistence" feature, you could make B something else (A overrides it, so that you can get back to your default NAND, so, I'd recommend leaving Luma on A, because without the override, you would have to power down just to leave your non-default NAND). There's individual scripts under the "Change A Hotkey" option, or you can use the "Change All Hotkeys" script (you can just hit B for any hotkey you don't want to change). The only keys you can't change are select (so you can get to Luma's configuration menu), L (so you can access the non-default NAND in Luma), and R (that's to reset to the default hotkeys in case, say, you mess up and forget to assign one to GodMode9 -- I've tried to make it difficult to paint yourself into a corner).

 

[mijuu]

edited

 

[mijuu]

EmuNAND is not proprietary. It contains zero patches. All CFWs (including Gateway mode) that support EmuNAND boot the same ones. CFWs do all of their patching in memory. There is no such thing as Luma EmuNAND or GW EmuNAND. There is just EmuNAND. Luma's chainloader is always going to boot into Luma by default (one of the primary reasons I don't use it). You have to use a real chainloader like BootCTR9 or CBM9 to get a choice of what CFW (or other app) boots by default. If you need an example of this, look up my InScripted AIO (that iso site, "CFW Discussion" section). Just copy the configuration over from "B9S Configurations" that matches your hardware. It boots Luma by default, Gateway on B, and GM9 is on left (among other things, a full list is included in the "ReadMe.txt" file). However, if you go into GM9, hit home, and select the Scripts menu, under "Default Payloads & Hotkeys" you will see an option to change the default payload. You can make it Gateway (or anything else).

If you do that, you no longer need Gateway on B. So you might want to reassign that hotkey. Luma's already hotkeyed to A as well, so unless you have a use for the "persistence" feature, you could make B something else (A overrides it, so that you can get back to your default NAND, so, I'd recommend leaving Luma on A, because without the override, you would have to power down just to leave your non-default NAND). There's individual scripts under the "Change A Hotkey" option, or you can use the "Change All Hotkeys" script (you can just hit B for any hotkey you don't want to change). The only keys you can't change are select (so you can get to Luma's configuration menu), L (so you can access the non-default NAND in Luma), and R (that's to reset to the default hotkeys in case, say, you mess up and forget to assign one to GodMode9 -- I've tried to make it difficult to paint yourself into a corner).

Thanks that worked a treat!

 

[1alien1]

Kazuma, quick question. I can use the same files from the AIO5 installer which i used on my n3dsxl on a 2ds with the O3DS files? Im unsure because it says o3ds but its a 2ds .
thank you!

EDIT: i installed and everything works finde. one question. can i reset the 2ds now after setting up luma and everything? i mean reset to factory? or will everything be erased? i bought the 2ds used and forgot to reset before hacking...:I

 

[Kazuma77]

Kazuma, quick question. I can use the same files from the AIO5 installer which i used on my n3dsxl on a 2ds with the O3DS files? Im unsure because it says o3ds but its a 2ds .
thank you!

EDIT: i installed and everything works finde. one question. can i reset the 2ds now after setting up luma and everything? i mean reset to factory? or will everything be erased? i bought the 2ds used and forgot to reset before hacking...:I

Sorry for not noticing your post sooner. You won't lose the exploit if you do a system format, but I believe the system will format the card (though you could just remove the card and boot Luma from CTRNAND). You could use TinyFormat as an alternative, but that may keep more than you want it to (it's mainly for unlinking purposes, so, it keeps things like DSiWare, and may also keep the NNID, I forget).

 

[1alien1]

Sorry for not noticing your post sooner. You won't lose the exploit if you do a system format, but I believe the system will format the card (though you could just remove the card and boot Luma from CTRNAND). You could use TinyFormat as an alternative, but that may keep more than you want it to (it's mainly for unlinking purposes, so, it keeps things like DSiWare, and may also keep the NNID, I forget).

Thank you !

 

[Arnold101]

how this method works? i don't have a emunand i can install without it?