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

[Hayleia]

I don't really understand the screen-init thing, but if you followed Plailect guide, you should not have any problem.

If he followed it recently, he should have problems on the contrary. The guide was updated to install a9lh v2 even though it's incompatible with Gateway.

But you know, this guide is a guide for the masterrace setup (free a9lh sysNAND only CFW), not for any setup. It has no breakpoint to a usable menuhax setup, uses RedNAND instead of EmuNAND for no reason, removes your RedNAND in the end because f*ck paranoids and uses an a9lh setup that doesn't work with Gateway...

I understand it can't put a lot of "if you want that, jump here instead of there" but it could easily
1) use emuNAND instead of redNAND (for GW compatibility)
2) add "inject FBI" steps to part 3 so we can stop after part 3 to have a usable setup (doesn't add anything, just moves it)
3) not update a9lh if it breaks compatibility with stuff, otherwise I don't see why it doesn't use rxTools instead of Luma, just for the sake of breaking things
4) make the last part about removing emuNAND not compulsory

 

[PiXi]

ok, that's bad, how to make my current setup compatible with GW payload? emuNAND is obligatory for GW?

 

[Tiibz]

ok, that's bad, how to make my current setup compatible with GW payload? emuNAND is obligatory for GW?

Use SafeA9LHInstaller v1 (not v2) and the v1 payload and files (very important, don't use v1 payload with v2 installer and vice-versa)
Emunand isn't mandatory, but launcher 4.0b will give you warning every time you wanna start sysNand

 

[PiXi]

Thanks! So I already have installed a9lh using SafeA9LHInstaller v2 how to properly reinstall it using v1? Just run from Homebrew menu?


https://github.com/AuroraWright/Saf...es/download/v1.5.2/SafeA9LHInstallerv1.5.2.7z

1.5.2.7 is ok?

Can't find payload_input.zip for v1

 

[Hayleia]

Thanks! So I already have installed a9lh using SafeA9LHInstaller v2 how to properly reinstall it using v1? Just run from Homebrew menu?


https://github.com/AuroraWright/Saf...es/download/v1.5.2/SafeA9LHInstallerv1.5.2.7z

1.5.2.7 is ok?

Can't find payload_input.zip for v1

I'd say you should restore a pre-a9lh 9.2 backup then load SA9LHI v1 from homebrew launcher yeah.
And here's an old version of the guide.
https://github.com/Plailect/Guide/w...hax)/2aa4abe44b812609c4482c87b3fb3d9257fb9053

 

[Just3DS]

For those who got A9LH v2 and want to use GW on it you can follow this guide by Cosmic_Link instead of going back to A9LH v1

https://gbatemp.net/threads/downgrade-custom-firmware-is-it-possible.430576/page-2#post-6439675

 

[PiXi]

Thanks! But I heard that any boot manager will block GBA support of LUMA3DS, is it true?

https://github.com/AuroraWright/Luma3DS/wiki/Installation-and-Upgrade

(Optional) Making Luma3DS work with an external boot manager
If you're using a boot manager (BootCtr9, CtrBootManager9, ARM9Select, etc.) to load Luma3DS, you won't be able to play GBA/DSiWare games, or certain games that need more RAM on the device (such as Super Smash Bros).

 

[Emenaria]

Thanks! But I heard that any boot manager will block GBA support of LUMA3DS, is it true?

https://github.com/AuroraWright/Luma3DS/wiki/Installation-and-Upgrade

(Optional) Making Luma3DS work with an external boot manager
If you're using a boot manager (BootCtr9, CtrBootManager9, ARM9Select, etc.) to load Luma3DS, you won't be able to play GBA/DSiWare games, or certain games that need more RAM on the device (such as Super Smash Bros).

Yeah, but you can use the pathchanger program to change the payload path manually and make Luma3DS work with GBA/DSiWare games. Or you can simply download your desired payload path using this site http://luma3ds.ericchu.net/ or this homebrew application https://github.com/Hamcha/lumaupdate

 

[Hayleia]

Thanks! But I heard that any boot manager will block GBA support of LUMA3DS, is it true?

https://github.com/AuroraWright/Luma3DS/wiki/Installation-and-Upgrade

(Optional) Making Luma3DS work with an external boot manager
If you're using a boot manager (BootCtr9, CtrBootManager9, ARM9Select, etc.) to load Luma3DS, you won't be able to play GBA/DSiWare games, or certain games that need more RAM on the device (such as Super Smash Bros).

Lol, the link you've given describes exactly how to fix this.
But it's true that there is no "to fix this, do this" between "there is a problem when using a boot manager" and the steps to fix the problem...

 

[kibin]

Has so many time I dont play on my 3DS... Now, months later I came here and saw this GW4.0. I don't understand why make a downgrade the system, I have O3DS 4.5 with GW3.7.1. I really need to make do that? And why?

 

[jerrmy12]

If he followed it recently, he should have problems on the contrary. The guide was updated to install a9lh v2 even though it's incompatible with Gateway.

But you know, this guide is a guide for the masterrace setup (free a9lh sysNAND only CFW), not for any setup. It has no breakpoint to a usable menuhax setup, uses RedNAND instead of EmuNAND for no reason, removes your RedNAND in the end because f*ck paranoids and uses an a9lh setup that doesn't work with Gateway...

I understand it can't put a lot of "if you want that, jump here instead of there" but it could easily
1) use emuNAND instead of redNAND (for GW compatibility)
2) add "inject FBI" steps to part 3 so we can stop after part 3 to have a usable setup (doesn't add anything, just moves it)
3) not update a9lh if it breaks compatibility with stuff, otherwise I don't see why it doesn't use rxTools instead of Luma, just for the sake of breaking things
4) make the last part about removing emuNAND not compulsory

The guide is for A9LH

 

[Hayleia]

The guide is for A9LH

Errm, ok.

But then, if that's just an a9lh guide, it should get you back to your starting point, with just the detail that you now have a9lh. So ok, get rid of redNAND and stuff... but never mention Luma, never mention Uncart and friends to put in /luma/payloads/ named key_name.bin, etc, because they have nothing to do in a guide that tells you how to install a9lh. Or ok, still name Luma because otherwise the console isn't really usable, but the point about the other ones not being necessary to mention still applies.

Well this guide does all of that, so it's not an a9lh guide, that's a guide that leads you to a certain setup it thinks is the best...
And I won't argue it isn't, because it is for the non-paranoid ones who don't have a Gateway (non paranoid don't care about emuNAND/redNAND and that allows better GBA VC, and no Gateway means a9lh v2 works). But there are paranoid people and people with Gateways so why not take them into account?
And do not use the argument "do not use a Gateway, do you not see how they try to lock you to their setup?" when I'm saying this guide does the same...

 

[PiXi]

Unfortunately I'm not completely understand this thing with pathchanger, could someone please show an example how to use it properly to run GW?

 

[GoodCookie88]

Has so many time I dont play on my 3DS... Now, months later I came here and saw this GW4.0. I don't understand why make a downgrade the system, I have O3DS 4.5 with GW3.7.1. I really need to make do that? And why?

Um ok so... Your asking if you should upgrade to gw 4.0 correct?

 

[PiXi]

Sorry to stupidity, I don't get the concept of using pathchanger with boot managers.

I know that Luma3DS allows us to load certain payloads just holding certain button during boot but... pathchanger is different thing...

Yeah, it's suck to be stupid.

 

[Hayleia]

@PiXi
Just use a boot manager (not the one provided by Luma but probably BootCTR as the steps say so (even though other people said that restoring a NAND backup then installing a9lh v1 worked too)) to boot Luma and Gateway.
Now, you'll just notice that Luma fails at doing some stuff, and the reason for this is that Luma thinks it's the main arm9loaderhax.bin (the one at the root) even though it's not.
That's where you use the pathchanger, just on Luma, to fix the fact some things don't work, by telling it that no, it isn't the main arm9loaderhax.bin but instead it is, say, /luma/arm9loaderhax.bin.

 

[SirByte]

I'm planning to do the following to my 4.1.0U o3DS (n3DS is at A9LH with 11.0.0U SysNAND and 11.0.0E RedNAND for European CIAs):

- Fix modified AGB_FIRM and TWL_FIRM
- Upgrade to 9.2.0U and create a NAND dump
- Follow Plialect's guide, except after the 2.1.0 OTP part, going back to 9.2.0U
- Install v1 of A9LH
- Install Luma3DS arm9loaderhax on my regular SDCard with 11.0.0U RedNAND
- Use GW's arm9loaderhax.bin on a separate SDCard with 11.0.0U EmuNAND (yes I already have one with Pasta, no I don't mind swapping)

That *should* give me one SD card with Luma, where GBA and DSiWare works (when installed to SysNAND) and one SD card with GW, where everything works what is working now (4.1.0U-MSET+11.0.0U EmuNAND ==> 9.2.0U-A9LH+11.0.0U EmuNAND) with the benefit being on the latest version of GW, not having to worry about the MSET or any other entrypoint anymore), and being able to update the RedNAND (to e.g. 11.1.0U) while leaving the EmuNAND on 11.0.0U, waiting for GW support.

Anything I should do differently?

 

[medoli900]

If he followed it recently, he should have problems on the contrary. The guide was updated to install a9lh v2 even though it's incompatible with Gateway.
-Snip snip-

How recent is the update?

 

[Temptress Cerise]

How recent is the update?

6-7~ish days ago was when v2 A9LH was added properly to Plailect's A9LH Guide.

 

[PiXi]

@Hayleia
Thank you! Now it's clear.