High failure rate when booting Gateway.firm

[TheShadowRunner]

Hi,
I use BootCtr9 to either boot Luma.firm or Gateway.firm (using pretty much all default BootCtr9 config settings, only the path is set).

While Luma boots perfectly 100% of the time, it's not the same at all when it comes to Gateway.firm..
Out of trying to boot 10 times, GW.firm will maybe boot 4 ot 5 times if I'm lucky which is a pretty big failure rate (when it fails, it gives a black screen and force power-off holding Power button is required).

I was wondering if it's due to BootCtr9 or if anything can be done to improve this?
Thanks for your support.

Gateway.zip

[urherenow]

The problem is that the Gateway.firm isn't a proper firm. It's a hack with ONLY the payload portion needed to launch the GW loader (.3dsx file, maybe? I forgot). It doesn't do any of the initial hardware setup or screen init or anything. Just ended up here because I decided to give fastboot3ds a try and couldn't get it to work at all, but it turns out it just doesn't work with quiet mode. In quick mode, you have to hold whatever button you set for bootCTR9, and let go of it as soon as you hit the power button. Hold on to that button too long, and the screen will stay black after the GW splash screen.

You can always play with the key delay in the boot_config file I guess. You can also go through the trouble of using fastboot3ds normal mode (choosing the bootCTR9.firm from within the menu) and you'll have pretty much 100% success, and a proper splash screen too. Using quick boot, the splash screen is scrambled every time.

Find someone who can figure out how to inject that gateway.firm into a PROPER .firm, and you won't even need bootCTR9 for it.