Hacking [RELEASE] GATEWAY 4.0 BETA (Private Beta Program)

[medoli900]

It's like the BOOT2 on wii. You can boot program through payload (if I understand) before the actual kernel is booted on 3DS. So you can unbrick a 3DS if you made a backup of the NAND, which you should have. Also, on Luma3DS, you can be on updated SysNAND and still have the signature check patch, but I don't know if it is true for GW. I THINK you still have A9LH after updating, so downgrading would be still possible if you update.

 

[sj33]

What does A9LH actually do for your 3ds? I know nothing about it so for example when I have gone through the steps with Gateway on the N3DSXL and I have downgraded to 2x and got to these points at the end>

• Go to A9LH Installer menu option again, follow instructions on screen until congratulations message appears.
• Reboot your console and enjoy GATEWAY A9LH on your N3DS (what do I do after this point)

Can I then update my systemnand to 11x and GW will work or something on systemnand not emunand anymore? sorry for being newbish but I really have not got a clue what it does for you.

Also in GW's instructions it mentions nothing about your region Time Machine packs do you need those on your SD Card as well as the other two? where do they go? or are they not necessary anymore with 4.0b.

You can still use EmuNAND if you want, but the whole point is that you can update your SysNAND to 11.0 - no need for EmuNAND anymore.

 

[Temptress Cerise]

You can still use EmuNAND if you want, but the whole point is that you can update your SysNAND to 11.0 - no need for EmuNAND anymore.

There is a nag when you try to use sysNAND using the 4.0b Launcher.dat. So it can be assumed that they don't want you updating sysNAND if you only use their solution. I wouldn't update using sysNAND with GW, no matter the version. Either use Luma3DS, or keep your emuNAND if you only want GW A9LH.

 

[Reecey]

You can still use EmuNAND if you want, but the whole point is that you can update your SysNAND to 11.0 - no need for EmuNAND anymore.

OK thanks so you can then update your systemnand to 11x after the last point and GW will work in systemnand but also you can use emunand if you want. Also sorry but do you need the data region pack on the route of your sd card as well it mentions nothing in the instructions.

 

[sj33]

There is a nag when you try to use sysNAND using the 4.0b Launcher.dat. So it can be assumed that they don't want you updating sysNAND if you only use their solution. I wouldn't update using sysNAND with GW, no matter the version. Either use Luma3DS, or keep your emuNAND if you only want GW A9LH.

Any word on if the new beta blocks FIRM writes? If not, you're gonna want to only update from within Luma anyway,

 

[veraci_00]

does the new a9lh gateway file (the one for those who r already on a9lh) brick the new 3ds if u update? also, how do I boot into decrypt 9 with that file intact? is there a way to designate a button to the new a9lh file with luma? thanks!

 

[medoli900]

Ok, I resolved my problem.
Anyone that has Menuhax installed at one point in their 3DS life should not use down to load GW payload. I used left and now it works. I guess it is because there is a remnant of Menuhax files installed on the NAND, and that that remnant is causing trouble with the payload.

 

[mvmiranda]

Yes it is working for me with Delebile's fork.

Hey, do you use updated sysNAND? Do you have emuNAND? What versions do you have (NAND, Launcher, etc)?

I'm asking because I'm 99% sure I don't have Delebile, since I installed A9LH right when it was made available.
I will redo my A9LH install this time following Plailect last part as it install Delebile's fork, but I need to know what "setup" I must choose, either updated sysNAND or emuNAND.

Thx!

 

[sj33]

This is curious, Does Gateway's new launcher have svcbackdoor included? Because PCSX seems to work with dynarec despite using 11.0.

 

[ihaveahax]

This is curious, Does Gateway's new launcher have svcbackdoor included? Because PCSX seems to work with dynarec despite using 11.0.

are you sure it's really using the 11.0 (2.51-0) FIRM?

 

[sj33]

are you sure it's really using the 11.0 (2.51-0) FIRM?

Oh good point. I wonder what Native firm it's using. Still the old 9.x?

 

[Migz]

Hi all, can someone please help me out here? i am trying to install this on a n3ds i get to the part where i try to install a9lh for the first time but it keeps saying my console emunand is not on 2x? I have downgraded it? what is going wrong here? Cheers

 

[ihaveahax]

Oh good point. I wonder what Native firm it's using. Still the old 9.x?

you could use my old crappy downgrade checker. it'll tell you the currently running NATIVE_FIRM version.

https://github.com/ihaveamac/downgrade-check/archive/v1.0.zip

 

[astronautlevel]

Any word on if the new beta blocks FIRM writes? If not, you're gonna want to only update from within Luma anyway,

Gateway does not write protect FIRM.

 

[sj33]

Gateway does not write protect FIRM.

So anybody using Gateway's own A9LH installer without an EmuNAND is screwed.

One more reason to avoid the Gateway installer.

 

[CropUpAnywhere]

I put the new folder on my console SC and now I'm menuhaxing straight into the time machine, will I be able to go into gateway mode from here after the downgrade?

 

[clock]

So I downloaded the .bin file to use with current Luma setup. I named it x_gw.bin (because I don't use uncart) and press X while power on my n3dsll and it boot to gateway sysnand beautifully (but I think it a bit slower than Luma but not too much). I played around a bit and all seems good but then when I went to System Setting to look and get out, I can't get the OSD menu to work anymore. So does this mean when exit from System Setting, it load the .bin file of Luma and not gateway payload?

 

[mvmiranda]

So I downloaded the .bin file to use with current Luma setup. I named it x_gw.bin (because I don't use uncart) and press X while power on my n3dsll and it boot to gateway sysnand beautifully (but I think it a bit slower than Luma but not too much). I played around a bit and all seems good but then when I went to System Setting to look and get out, I can't get the OSD menu to work anymore. So does this mean when exit from System Setting, it load the .bin file of Luma and not gateway payload?

I would assume so, since A9LH will rerun arm9loaderhax.bin, which is Luma3DS. Right?

 

[AkumaNoYami]

Doesnt work at my new 3ds 2 times i have reinstall all but it is the same : your emunand are not on 2.1 >

 

[mvmiranda]

Guys, I need a tip.
The old GW.3dsx didn't work with my previous A9LH setup (updated sysNAND with emuNAND 9.2 for *hax). So I had to change to a 9.2 sysNAND + A9LH (booting to emuNAND) and a "normal" 11.0 emuNAND and now booting holding L to sysNAND 9.2 then choosing GW.3dsx works. Back then I didn't know what was "causing" this.

So, as I posted some posts above, now I believe this was because I was running some other A9LH fork other than Delebile's, and for this very same reason the new GW arm9loaderhax.bin will not work with my A9LH setup even if I update my sysNAND to 11.0 and boot directly to it.

So I will redo my A9LH setup (yes, I do have hardmod and my otp.bin) but this time I will use @Plailect guide.

The question now (and the tip I'm asking for) is if I should go for a updated sysNAND or continue using 9.2 sysNAND + emuNAND 11.0.

The goal is to have a working A9LH + Luma3DS with GW's arm9loaderhax.bin.

Thanks!