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

 

[CH1CK3NMAN]

Luma does not provide you with Gateway functionally... that is why we must "dual-boot" between both CFW... and I doubt we will ever have Gateway functionality on Luma... because I doubt they'd want to spend time RE Gateway's stuff in regards to that since there are free alternatives to what it does... such as NTR CFW's cheat plugin for cheats and CIA for games... and holding down L is reserved on Luma for booting your EmuNAND, while on Gateway's CFW it's reserve to go right into the menu... your only option if you want to boot while holding is to use another bootmanager like BootCTR9 and set it up, but using L is not advised, especially if a CFW has it reserved for something already....

As for if that link works, I don't know, and honestly just using something like Quick Reboot would probably be faster. As for updating your Red Card, it just updates it... Not sure why, but it should force you update it if your Red Card needs it...

What exactly is quick reboot?

 

[Temptress Cerise]

What exactly is quick reboot?

https://gbatemp.net/threads/homebrew-quick-reboot-cfw-gateway-ninjhax.379101/

 

[CH1CK3NMAN]

Thanks

 

[CH1CK3NMAN]

I have another quick question. Is it normal for settings to show Ver. 11.0 and not sys 11.0 when I'm using the gateway? When I reboot, it goes back to sys 11.0.

 

[Temptress Cerise]

I have another quick question. Is it normal for settings to show Ver. 11.0 and not sys 11.0 when I'm using the gateway? When I reboot, it goes back to sys 11.0.

The sys thing is a Luma3DS thing... It will not show up on Gateway Mode (CFW) as they don't implement such a thing for sysNAND...

 

[SOLSTAR]

i have an original gateway on a 3dsxl,with emunand,which works fine,but apparently for newer cia games,you need luma3ds or some stuff like that.

now is there a simpler version of whatever stuff you just posetd^i don't want to replace gateway nor to have one of those custom cfw bs made by someone.

i just want to boot straight into gateway mode,and then select whatever other cfw i want(on top of that)by cia method like i do already with NTR cfw

this guide here "https://github.com/Plailect/Guide/wiki/Part-5-(arm9loaderhax)"os overly and uslessly complicated

 

[Hayleia]

i have an original gateway on a 3dsxl,with emunand,which works fine,but apparently for newer cia games,you need luma3ds or some stuff like that.

now is there a simpler version of whatever stuff you just posetd^i don't want to replace gateway nor to have one of those custom cfw bs made by someone.

i just want to boot straight into gateway mode,and then select whatever other cfw i want(on top of that)by cia method like i do already with NTR cfw

this guide here "https://github.com/Plailect/Guide/wiki/Part-5-(arm9loaderhax)"os overly and uslessly complicated

No idea what you're talking about everywhere.
You don't need Luma for newer games.
If you don't want a cfw bs made by someone, forget about Gateway.
No idea what your sentence about the "cia method" and NTR means when we're talking about Gateway.
The guide isn't "overly and uselessely" complicated, all steps are needed. This unless more automation is involved, and that's why Gateway tried, and people got problems. So you can wait for "cfw bs" people to simplify the current method, risk your hand at Gateway's, or use the "overly and uselessly complicated" one, your choice.

 

[SOLSTAR]

No idea what you're talking about everywhere.
You don't need Luma for newer games.
If you don't want a cfw bs made by someone, forget about Gateway.
No idea what your sentence about the "cia method" and NTR means when we're talking about Gateway.
The guide isn't "overly and uselessely" complicated, all steps are needed. This unless more automation is involved, and that's why Gateway tried, and people got problems. So you can wait for "cfw bs" people to simplify the current method, risk your hand at Gateway's, or use the "overly and uselessly complicated" one, your choice.

in fact i never needed this thing.but now i was trying dragon ball fusion,which i have only in .cia format,and halfway during the installation its says the file is corrupt.same thing for many other users EXCEPT a few who said that with luma and a9lh whatever that name is,it works and run fine

 

[Hayleia]

in fact i never needed this thing.but now i was trying dragon ball fusion,which i have only in .cia format,and halfway during the installation its says the file is corrupt.same thing for many other users EXCEPT a few who said that with luma and a9lh whatever that name is,it works and run fine

What is your setup exactly?
O3DS? N3DS?
MSET? menuhax? a9lh (though I guess not that one)?
3.7.1? 4.0? 4.1?
emuNAND firmware version?

And actually, even if you're using all latest stuff from Gateway, maybe the problem comes from the SD card. But I've never heard of anything that runs on Luma and not Gateway before today (well, except when there was that whole 9.5 crypto thing on N3DS, but this has been fixed everywhere).

Anyway, if you want to install a9lh+Luma, I won't stop you, but I don't see why that would solve your problem.

 

[mijen]

I only recently began getting involved CFW for my O3DS (mostly lurked) but feel like I am misunderstanding a lot of the terminology.

I followed Plailect's guide to the tee and now I am on Sys 11.0.0-33U (I am understanding Sys to mean emunand). Does this method give any exception to being able to run a Gateway card on EmuNand 11.0.0-33U? I have found other threads on this website that says it is no problem running due to Luma3DS patching TWL_FIRM? I have done everything correctly: able to get to the red dragon screen, hold L to get to the "Gateway 3DS ULTRA v3.7.1". But, as soon as i click "Boot Gateway Mode" screen doesn't go black but loads up the 3DS home menu screen with settings indicating "Ver 11.0.0-33U" (I assume this to be the SysNand?)

From everything I have read so far, no one has mentioned this being a problem. I haven't really done anything with the GW red or blue card. I placed my own .3ds game into the root of a microSD card and then into the red card. I am very hesitant on making any modifications via the GW menu thing I mentioned earlier because lack of directions.

Sidetopic: If I followed Phailect's guide to the end, is downgrading 11.0.0-33U still impossible without hardmod? I was reading it over it doesn't really differentiate the difference between being on 11.0.0-33U pre-Luma3DS or post-Luma3DS. I do see Ver 11.0.0-33U (this one concerns me) and Sys 11.0.0-33U in the settings depending on how I boot. I only ask because if the above GW issue cant be resolved and I cant downgrade, I am stuck playing with CIA installed games (personal preference for flashcarts)

EDIT: ...held start and Gateway menu appears with the .3ds file I put on the SD Card. But doesn't seem to do anything when I click "A" on the game file and shows a little loading bar.

 

[Temptress Cerise]

I only recently began getting involved CFW for my O3DS (mostly lurked) but feel like I am misunderstanding a lot of the terminology.

I followed Plailect's guide to the tee and now I am on Sys 11.0.0-33U (I am understanding Sys to mean emunand). Does this method give any exception to being able to run a Gateway card on EmuNand 11.0.0-33U? I have found other threads on this website that says it is no problem running due to Luma3DS patching TWL_FIRM? I have done everything correctly: able to get to the red dragon screen, hold L to get to the "Gateway 3DS ULTRA v3.7.1". But, as soon as i click "Boot Gateway Mode" screen doesn't go black but loads up the 3DS home menu screen with settings indicating "Ver 11.0.0-33U" (I assume this to be the SysNand?)

From everything I have read so far, no one has mentioned this being a problem. I haven't really done anything with the GW red or blue card. I placed my own .3ds game into the root of a microSD card and then into the red card. I am very hesitant on making any modifications via the GW menu thing I mentioned earlier because lack of directions.

Sidetopic: If I followed Phailect's guide to the end, is downgrading 11.0.0-33U still impossible without hardmod? I was reading it over it doesn't really differentiate the difference between being on 11.0.0-33U pre-Luma3DS or post-Luma3DS. I do see Ver 11.0.0-33U (this one concerns me) and Sys 11.0.0-33U in the settings depending on how I boot. I only ask because if the above GW issue cant be resolved and I cant downgrade, I am stuck playing with CIA installed games (personal preference for flashcarts)

EDIT: ...held start and Gateway menu appears with the .3ds file I put on the SD Card. But doesn't seem to do anything when I click "A" on the game file and shows a little loading bar.

Gateway Mode will always show Ver. when booting into a SysNAND environment.
Luma3DS will show Sys when booting into a SysNAND environment and with the following option checked off: "Show current NAND in System Settings" in Luma's Config.
Luma3DS will show Emu if you are booting a EmuNAND environment. Do you not recall part 3 of Plailect's A9LH Guide? https://github.com/Plailect/Guide/wiki/Part-3-(RedNAND) - An EmuNAND//RedNAND environment will show Emu.

So yeah, as far as Luma3DS goes, you do seem to be misunderstanding the terminology. And if you followed the A9LH to the very end without skipping anything, then your system is now a SysNAND-Only A9LH setup.

As for differences between pre-Luma3DS and post-Luma3DS, I am not even sure what you mean by this. The goal of Plailect's A9LH Guide is to have you setup with the best possible A9LH setup, which is a SysNAND Only environment, with no EmuNAND//RedNAND, since with A9LH, having an EmuNAND//RedNAND is pretty useless. The guide uses Luma3DS, as it's a pretty Noob-Proof CFW.

As for the loading issue, I don't know, mine works, it shows the bar for a brief second on some games and for a second or two on other games, and then it just appears in place of where the blank cartridge spot was.

 

[cooroxd]

Hi, I put all the necessary files in the right places but I keep getting a black screen after the dragon logo pops up. edit: Nevermind, i figured it out, I had remnant of the rednand that I didn't properly delete.

 

[koyuki38]

Hi
Thanks for this tuto, i'll try it soon.

Can you explain how it works ?
I mean, this page https://github.com/AuroraWright/Luma3DS/wiki/Other-features-and-notes#payload-chainloading says we have to take the payload we want and rename it regarding the button we want to use.
So why is the payload from v2gw.zip needed ?

Also as you talk about BootCTR9 in the begining of the tuto, i don't see any of it in the steps. Do we use BootCTR9 or not with this method ?

(Edit : It worked perfectly but the question is still up)

 

[gohan127]

thanks for the guide! it works great on my n3dsxl i installed a couple of months ago. unfortunately the new BOOTCTR9 V1.0 stays stuck at the BOOTCTR9 loading screen. i had to install the older version for it to load the GW.bin.
doe anybody have a solution to make BOOTCTR9 V1.0 work with gateway?

 

[Chrisssj2]

Thanks this is great!!! I heard though that if i use this, that UNDER NO CIRCUMSTANCE. I should update. they disadvise of using this.
Here is screenshot
www.imagebam.com/image/944c61501272142

 

[Temptress Cerise]

Thanks this is great!!! I heard though that if i use this, that UNDER NO CIRCUMSTANCE. I should update. they disadvise of using this.
Here is screenshot
www.imagebam.com/image/944c61501272142

Yeah, never update SysNAND while in GW-Mode, this is because GW does not have FIRM protection, so you'll either end up bricking or going to a stock vanilla system if you update.

thanks for the guide! it works great on my n3dsxl i installed a couple of months ago. unfortunately the new BOOTCTR9 V1.0 stays stuck at the BOOTCTR9 loading screen. i had to install the older version for it to load the GW.bin.
doe anybody have a solution to make BOOTCTR9 V1.0 work with gateway?

I guess contact the BootCTR9 dev and mention that the previous version worked but the newest one doesn't?

Another trick is to use the v2gw.bin, you could use HxD to change the path it points to from /luma/payloads/gateway.bin to /a9lh/payloads/gateway.bin, think someone has done this before for one of their setups.

Hi
Thanks for this tuto, i'll try it soon.

Can you explain how it works ?
I mean, this page https://github.com/AuroraWright/Luma3DS/wiki/Other-features-and-notes#payload-chainloading says we have to take the payload we want and rename it regarding the button we want to use.
So why is the payload from v2gw.zip needed ?

Also as you talk about BootCTR9 in the begining of the tuto, i don't see any of it in the steps. Do we use BootCTR9 or not with this method ?

(Edit : It worked perfectly but the question is still up)

BootCTR method is a whole other thread and is sort of linked towards the end, I guess I could update this one to include that. However, it lookks like the latest version of BootCTR9 breaks native support for Gateway's a9lh.bin.

 

[vigi_lante]

Yeah, never update SysNAND while in GW-Mode, this is because GW does not have FIRM protection, so you'll either end up bricking or going to a stock vanilla system if you update.

In that case, isn't better to just install an Emunand, since the Gateway launcher will always boot to the Emunand? So the SysNAND will be intact if you update accidentally.

 

[Hayleia]

In that case, isn't better to just install an Emunand, since the Gateway launcher will always boot to the Emunand? So the SysNAND will be intact if you update accidentally.

Depends. Some people like to have GBA VC and all on one NAND (to have one folder only in Nintendo 3DS, easier management or whatever).
If you don't, yeah, an emuNAND suits your needs.

 

[hippotamamus]

weird, i can enter gateway red menu with R button but i cant load gw menu with L button, its keep loading to home screen

 

[Hayleia]

weird, i can enter gateway red menu with R button but i cant load gw menu with L button, its keep loading to home screen

Are you using the very latest Launcher from Gateway? Because in that case, it's L+SELECT to enter the menu.