The guide says to format twice. You could use FBI.3ds, but you would have to switch between Gateway Mode and Luma since the actual downgrade has to be done with Luma. FBI injection is very easy and for a newb it's better to follow the guide exactly so there's less chances of screwing something up.
Actually, you CAN use GW 4.0 because the firm protection is removed. Also, if you want something that stays in place, just install ApacheThunder's NAND DevMenu (search for "Dev Mega Pack" on a certain iso site). Just use BBM to install it. FBI goes by the first 8, ignoring the 2 at the end of the title ID, and installs it to SD because it's an app/game (at least, that's what it appears to do).
Why not try BootCTR? It should make it work with people who have no screen-init. Kazuma77 said he uses a no-screen init fork and at the link below is his config.
Link:
https://gbatemp.net/threads/the-status-of-gateway-and-a9lh.427889/page-56#post-6408904
I was using no init, but it broke the CBM9 part of my configuration, containing the stuff I use less often, so I went back to the original screen init files.
Thanks! So it would be better to install Luma first and then add GW's arm9loaderhax.bin as another booting method later?
I want to be abled to autoboot to GW and when I press the "L"-button on startup Luma CFW shall boot. Is this possible? (Both using the same Emunand Partition)
Also if I use both Luma and GW with the same Emunand will it be possible to play GBA games whenever I boot into Luma CFW?
Use my BootCTR9 configuration
HERE if you want GW to run first. Luma has to be the default with Luma's chain loader (obviously). Just make "boot_config_gw.ini" the "boot_config.ini" (by default, it's setup for CFW). It's set to run Luma from A though, not L. You can change that, but I wouldn't recommend it. All hotkeys seem to work with A (seems to be the only hotkey anything likes for that matter, but I can easily delete the Cakes config file when I want to change things on that, so Luma it is). Or you could use
this in an unconventional way and make Luma your "a9lh/gw/arm9loaderhax.bin" file (or swap the payloads so that GW runs by default).
I was able to restore my nand with the newest gateway beta
Thanks for confirming that's fixed. And good to know you won't be needing a hard mod.
I think i am just going to be patient for now. As of this moment it doesn't really offer me anything that i would trade the safety of an Emunand for.
I personally think the tool "CIAngel" is far more revolutionary than the whole A9lhx.
You don't have to "trade the safety of an EmuNAND" for it. You can simply restore EmuNAND_original.bin to EmuNAND instead of restoring it over your SysNAND with the "keep A9LH" setting, and not delete EmuNAND. Consider any part of the guide beyond the actual A9LH installation a suggestion, not something you have to do.
You should update your wishlist on your signature.
As for me, I just want them to remove the sysNAND nag, or make it an option we can check off.
Exactly. If they can detect that you're running A9LH, why not just have it enable firm protection instead of showing a nag?
