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

  • Thread starter Thread starter Traiver
  • Start date Start date
  • Views Views 109,741
  • Replies Replies 695
  • Likes Likes 12
if you can do a hardmod and Gateway saves your OTP.bin to your SD Card (I am not sure if it does), you should be able to make a pre-A9LH NAND backup on 9.2, then use GW's A9LH installer.
afterward, you can flash the pre-A9LH NAND backup then use SafeA9LHInstaller with your OTP.bin and install the A9LH branch from @Plailect's guide. (follow the A9LH install section of his guide)

EDIT: it seems that hardmod NAND backups may not work right once GWs A9LH is installed, I would either use the A9LH guide or wait until people can confirm or deny this.

Beta testers have said that trying to use a hardmod fails because gw blocks the nand from being altered while the 3ds isnt booted up. Or so ive seen.
Well feck, that ain#t good. guess i'll hold off so.
 
So, Gateway didn't implement FIRM0/FIRM1 write protection. So, you downgrade to 2.1, and instead of at least being able to get back to 9.2 somehow, you install Gateway's version A9LH on 2.1. Guess what? If you're on an Old 3ds, you might brick your console by updating, or lose A9LH. And if you try and update on a New3ds, you'll definitely brick. So lucky Gateway A9LH users get to be stuck on 2.1! I'm glad Gateway's trying to get involved in what's current, and their arm9loaderhax.bin file is a step in the right direction, but seriously; who would install their version of A9LH? Although, now that I think about it, Gateway users would still be able to use their emuNAND. But isn't one of the advantages of A9LH that you don't need an emuNAND? Final thought: I'll just stick to their arm9loaderhax.bin file.
a9lh was not new in the sense of letting us use sysnand...
gw only ran on sysnand years ago. we have never needed emunand.
a9lh is nice because it works independently of the firmware version. so, 11.0, 12.0 etc.
 
Well feck, that ain#t good. guess i'll hold off so.

Am I missing something here?
If you can hardmod the console, I see no reason to not follow the A9LH guide as it is hard to mess it up and the NAND can be restored via a hardmod if anything goes wrong.
you do not need to hardmod it either unless something goes wrong and you need to flash the NAND backup.
 
If I don't have EmuNAND on my SD card, I find that at least with Gateway's arm9loaderhax.bin, I cannot boot Gateway. It shows the Gateway logo, then stays stuck on a black screen. This problem happens both with a boot manager, and with directly booting to the arm9loaderhax.bin.

The workaround is to boot Gateway with L held to go to the Gateway menu, then explicitly boot SysNAND from that. It won't automatically switch to SysNAND if you don't have EmuNAND.

This does not give me the warning about updating in SysNAND. In fact, anyone who gets this warning, how did they boot Gateway to get it? I can't trigger it, and I'm definitely running 4.0b. Does it only show up when you don't use arm9loaderhax.bin?
 
Last edited by Jiro2,
a9lh was not new in the sense of letting us use sysnand...
gw only ran on sysnand years ago. we have never needed emunand.
a9lh is nice because it works independently of the firmware version. so, 11.0, 12.0 etc.
Fair enough. But I was more referencing the fact that A9LH really has no need for emuNAND whatsoever. You can update your sysNAND all you want (most of the time...), because now you can get kernel access above 9.2, meaning you don't need to rely on an emuNAND for access to the latest update. (There's more, but I'm lazy and I would rather not type any more than necessary.)

--------------------- MERGED ---------------------------

Am I missing something here?
If you can hardmod the console, I see no reason to not follow the A9LH guide as it is hard to mess it up and the NAND can be restored via a hardmod if anything goes wrong.
you do not need to hardmod it either unless something goes wrong and you need to flash the NAND backup.
The problem is Gateway is trying to lock their users down and force them to continue the usage of Gateway's products. That is rather revolting to me.

EDIT: I assumed that wouldn't be a double post...oh well.
 
Okay. New payload! Hooray!
I'm a total noob at A9LH, even though I followed Plailect's guide months ago I still don't understand how a payload works and how I can set buttons to load one. Would anybody be kind enough to teach me?

I have Luma3DS with the button for decrypt9, emunand9 etc set up and I have Liomajor's unofficial payload to load gateway with X+Y.

I would like to know how to autoboot gateway and Luma for other buttons and backwards. Just in case.
 
If I don't have EmuNAND on my SD card, I find that at least with Gateway's arm9loaderhax.bin, I cannot boot Gateway. It shows the Gateway logo, then stays stuck on a black screen. This problem happens both with a boot manager, and with directly booting to the arm9loaderhax.bin.

The workaround is to boot Gateway with L held to go to the Gateway menu, then explicitly boot SysNAND from that. It won't automatically switch to SysNAND if you don't have EmuNAND.

This does not give me the warning about updating in SysNAND. In fact, anyone who gets this warning, how did they boot Gateway to get it? I can't trigger it, and I'm definitely running 4.0b. Does it only show up when you don't use arm9loaderhax.bin?
I got the nag on 4.0b, and I don't have an emuNAND. From what you wrote, it sounds like you didn't properly remove emuNAND. You have to use emuNAND9's "Format SD (No Emunand)" to properly remove an emuNAND.

Another person had the same problem your describing.
Link: https://gbatemp.net/threads/the-status-of-gateway-and-a9lh.427889/page-55#post-6408813
And this is after they properly removed emuNAND.
Link: https://gbatemp.net/threads/the-status-of-gateway-and-a9lh.427889/page-56#post-6409017

Edit: I used the "arm9loaderhax.bin" provided by Gateway. Directly, as a Luma payload and with CtrBootManager9, with the 4.0b Launcher.dat, all three methods gave me the nag. Using 4.0a Launcher.dat to avoid the nag, and boots just fine to sysNAND.
 
Last edited by Temptress Cerise,
I tried this and it *did* work, even though the ctrbootmanager9 I was using did not work. What's the difference between the two?

I found the v1.1 dshoe build didn't work for me, but the original v0.5 that cpasjuste put out works fine (and also works with all my other updated payloads), so sticking with that.
 
I still stuck at Wifi config on n3ds even though I go to GW Mode and browsing their website with browser but when I run their app it's keep saying Fatal Error : config Wifi blabla. Anyone have the same with me ?
 
I followed Plailect guide to have A9LH on my N3DS with Luma3DS. The only thing I need is to be able to have the GW menu. Is it possible with my current setup?
 
If the people who are saying that "GW doesn't let you use a hardmod" are referring to dax's case then that was due to an issue with his hardmod, not GW itself. Unless this is something new to this release.
 
  • Like
Reactions: daxtsu
I followed Plailect guide to have A9LH on my N3DS with Luma3DS. The only thing I need is to be able to have the GW menu. Is it possible with my current setup?
Yes. Just download the "arm9loaderhax.bin" provided by Gateway on their site. You'll also need the Launcher.dat, either 3.7.1 / 4.0a / 4.0b.

If you want to use Luma3DS Payload chainloading feature, then just rename it according to this.
Link: https://github.com/AuroraWright/Luma3DS/wiki/Other-features-and-notes#payload-chainloading

If you're using another bootmanager, you'll have to configure however they let you do that.
 
  • Like
Reactions: medoli900
I'm very new to this A9LH hack. I don't know what exactly is a payload, I only know that we can use button combination to load some program at boot with these, but I don't know where to put the payloads.
Download the arm9loaderhax.bin for GW, name it <button>_GW.bin, drop it in /luma/payloads. Hold <button> when booting to activate GW menu.
 

Site & Scene News

Popular threads in this forum