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

[urherenow]

So, I have a question, on part 5 of the A9LH setup, would you be able to use a backup of your own Gateway Emunand or do you have to use your Rednand emunand backup?

just wondering for experimental purposes.

If you're going to use a GW, you CAN'T use a REDNand. GW doesn't work with one.

I've been way out of the loop homebrew-wise, and wanted to find what benefit A9LH has since I know next to nothing about it. Anyway, I came across this Reddit thread. Apparently, dumping a console's OTP takes hours, yet it looks like Gateway's method doesn't even mention having to do anything like this. So did Gateway come up with a new method that isn't as slow, or are their instructions just really vague on details?

GW grabs your OTP into memory and upgrades/installs a9lh in one step. But then you are stuck using ONLY GATEWAY. You can't even use your system without it. Once you are on a working 2.1, it's best to use the guide to get your OTP, then upgrade, then install a9lh, and use GW's arm9loaderhax.bin when you want to use it. Chain loading it via Luma or a boot manager is best.

 

[Swiftloke]

'GATEWAY FAST BOOT'
No.... Just no...
Do I really need to explain why this is so bad.
Just call it a9lh. Don't give it some other name, a bad one at that, that makes it sound like you all invented it.
I hope I get the point across, the post was a bit ranty...

 

[ttr13]

If you're going to use a GW, you CAN'T use a REDNand. GW doesn't work with one.

GW grabs your OTP into memory and upgrades/installs a9lh in one step. But then you are stuck using ONLY GATEWAY. You can't even use your system without it. Once you are on a working 2.1, it's best to use the guide to get your OTP, then upgrade, then install a9lh, and use GW's arm9loaderhax.bin when you want to use it. Chain loading it via Luma or a boot manager is best.

Thanks, that's what I thought but didnt think it would hurt to ask. I'll just use Luma+ Gateway arm9

 

[NyaakoXD]

Wait, so how do you get Gateway's payload to work? I get the Gateway menu, but when I try to go into EmuNAND or SysNAND, it gets stuck on a black screen. (Already have A9LH installed through Plailect's guide)

 

[medoli900]

Wait, so how do you get Gateway's payload to work? I get the Gateway menu, but when I try to go into EmuNAND or SysNAND, it gets stuck on a black screen. (Already have A9LH installed through Plailect's guide)

How do you load your payload?
With Luma3DS? If so, which button do you press to loads the GW menu?

 

[NyaakoXD]

How do you load your payload?
With Luma3DS? If so, which button do you press to loads the GW menu?

I held the D-Pad Down.

 

[stl25]

Wait, so how do you get Gateway's payload to work? I get the Gateway menu, but when I try to go into EmuNAND or SysNAND, it gets stuck on a black screen. (Already have A9LH installed through Plailect's guide)

I have heard on these forums that for some reason the chainloader of Luma3DS does not work with the GW payload. I chose a long time ago to not use the Luma3DS chainloader and utilize @FIX94 arm9select (customized by me) for all my payload loading needs.

All my payloads are in a payloads folder on the root of mSD/SD and use the following buttons
Default = CFW.bin
the following buttons can be used: a,b,x,y,up,down,left,right,l,r,start and select
works great for me (though you need a A9LH which has screen init)

my setup in my sig

 

[Temptress Cerise]

I have heard on these forums that for some reason the chainloader of Luma3DS does not work with the GW payload. I chose a long time ago to not use the Luma3DS chainloader and utilize @FIX94 arm9select (customized by me) for all my payload loading needs.

All my payloads are in a payloads folder on the root of mSD/SD and use the following buttons
Default = CFW.bin
the following buttons can be used: a,b,x,y,up,down,left,right,l,r,start and select
works great for me (though you need a A9LH which has screen init)

my setup in my sig

Luma3DS's chainloader should work just fine on screen-init forks of A9LH. @LinkmstrYT says they can load up to the GW menu, but black screens after that, whether sysNAND or emuNAND. So I don't think the issue is with the chainloader.
Also, here are some setups I've tested: http://gbatemp.net/threads/moving-from-luma3ds-to-luma-gw.429549/#post-6414979

 

[medoli900]

I held the D-Pad Down.

That's the same problem I had :3
Change it to another direction, you probably have a remnant file of MenuHax.

I have heard on these forums that for some reason the chainloader of Luma3DS does not work with the GW payload. I chose a long time ago to not use the Luma3DS chainloader and utilize @FIX94 arm9select (customized by me) for all my payload loading needs.

All my payloads are in a payloads folder on the root of mSD/SD and use the following buttons
Default = CFW.bin
the following buttons can be used: a,b,x,y,up,down,left,right,l,r,start and select
works great for me (though you need a A9LH which has screen init)

my setup in my sig

You can use Luma3DS to chainload without any complication. There is just that little glitch with MenuHax that can be easily fixed.

 

[NyaakoXD]

That's the same problem I had :3
Chage it to another direction, you probably have a remnant file of MenuHax.

Pretty sure that's not it. I also used the X button (After moving the uncart payload somewhere else) and still get the same results (a black screen after trying to get into GW mode).

 

[stl25]

So GW users should be using a A9LH fork that has screen init.

I use @FIX94 A9LH fork which has screen init but sets backlight to 0. Useful with arm9select but not with Luma3DS chainloader as Luma3DS does not have anything built in to enable backlight like arm9select does.

 

[medoli900]

Pretty sure that's not it. I also used the X button (After moving the uncart payload somewhere else) and still get the same results (a black screen after trying to get into GW mode).

That is weird, because for me it worked like a charm. Try to rename the gateway payload file to "left_GW.bin" (that is how I named it) without the quotes (duh) and verify that you have gateway payload in ../Luma/Payload.

 

[NyaakoXD]

That is weird, because for me it worked like a charm. Try to rename the gateway payload file to "left_GW.bin" (that is how I named it) without the quotes (duh) and verify that you have gateway payload in ../Luma/Payload.

Still a black screen...

 

[medoli900]

Still a black screen...

Then I really don't know... Do you use GW 3.7.1 or 4.0b launcher.dat? I use 3.7.1 myself.

 

[NyaakoXD]

I tried using both, but they still ended up with black screens.

 

[medoli900]

Does it works without A9LH? (If you have another exploitable 3DS to test on it)
Maybe it is the flashcard itself or the MicroSD card that cause problem.
Also, would you mind sending me a picture of your (N)3DS MicroSD/SD card root? I would help me see if there is something different than mine that could create a conflict.

 

[NyaakoXD]

Does it works without A9LH? (If you have another exploitable 3DS to test on it)
Maybe it is the flashcard itself or the MicroSD card that cause problem.
Also, would you mind sending me a picture of your (N)3DS MicroSD/SD card root? I would help me see if there is something different than mine that could create a conflict.

It's fine... I'll just try again some other time. >_<;

 

[CreAtor135]

I've been way out of the loop homebrew-wise, and wanted to find what benefit A9LH has since I know next to nothing about it. Anyway, I came across this Reddit thread. Apparently, dumping a console's OTP takes hours, yet it looks like Gateway's method doesn't even mention having to do anything like this. So did Gateway come up with a new method that isn't as slow, or are their instructions just really vague on details?

I suppose you could say it's a mix of both. Gateway automates the process somewhat, but it seems they skip parts of Plail's guide.

 

[medoli900]

I suppose you could say it's a mix of both. Gateway automates the process somewhat, but it seems they skip parts of Plail's guide.

Not only skipping parts, but also completely disregard the unbricking process of the EmuNAND/RedNAND for N3DS. I would highly suggest to follow Plailect guide and then add Gateway's Launcher.dat at the root of SD card and then Gateway's payload to chainload it with Luma3DS.

 

[CreAtor135]

Not only skipping parts, but also completely disregard the unbricking process of the EmuNAND/RedNAND for N3DS. I would highly suggest to follow Plailect guide and then add Gateway's Launcher.dat at the root of SD card and then Gateway's payload to chainload it with Luma3DS.

It no longer does that, but it did before.