Hacking 4.5 o3ds + boot9strap + gateway??

[zhdarkstar]

Not a converted file, only tried something out and it works.
https://gbatemp.net/threads/tutorial-booting-gw-with-b9s-and-some-help.471417/

Thanks to @RednaxelaNnamtra for the firm version of bootctr9.

Worked like a charm once I realized that the first line of the boot_config.ini needed to be commented out.

 

[Shady Guy Jose]

You're wrong. I just tested that out on my Old3DS. And Moon launched just fine in GW Mode.

The only thing that sucks, is that with that method. After a reboot, you'll be launched into Luma3DS tho.

The only way to not let that happen is to completely forego using Luma3DS as the main .firm, and using BootCTR9.firm as the main one, and enabling it's Autosoftboot config.

Though, this was also true even with the old guide of mine.

True. I had read that somewhere, but I tested it and it's working. I want Luma as my main, so I'm golden. Ended up with just one more file.

 

[Temptress Cerise]

True. I had read that somewhere, but I tested it and it's working. I want Luma as my main, so I'm golden. Ended up with just one more file.

You'd still be able to use Luma3DS as your Main CFW with BootCTR9 tho.

Example boot_config.ini of that:

[BOOTCTR9]
screenEnabled = 1
screenLog = 0
fileLog = 0
key_delay = 1000
boot_splash = 1
boot_splash_image = /luma/splash.bin
screenBrightness = 0xFF
enableAutosoftboot = 1
enableSoftbootSplash = 0

;Luma3DS (SysNAND)
[DEFAULT]
path = /luma/Luma3DS.firm
delay = 100
enablePathFix = 1

;BrickWait Mode (EmuNAND)
[KEY_DDOWN]
path = /luma/payloads/BrickWait.bin
delay = 100

iirc, you can still access Luma3DS' config and payload chainloader as well.

 

[Shady Guy Jose]

You'd still be able to use Luma3DS as your Main CFW with BootCTR9 tho.

Example boot_config.ini of that:

[BOOTCTR9]
screenEnabled = 1
screenLog = 0
fileLog = 0
key_delay = 1000
boot_splash = 1
boot_splash_image = /luma/splash.bin
screenBrightness = 0xFF
enableAutosoftboot = 1
enableSoftbootSplash = 0

;Luma3DS (SysNAND)
[DEFAULT]
path = /luma/Luma3DS.firm
delay = 100
enablePathFix = 1

;BrickWait Mode (EmuNAND)
[KEY_DDOWN]
path = /luma/payloads/BrickWait.bin
delay = 100

iirc, you can still access Luma3DS' config and payload chainloader as well.

I know, but it's redundant. I have GodMode9 as up and BootCTR9+v2gw+gateway as down, with 0ms delays all around, and it works just fine for me.

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

You'd still be able to use Luma3DS as your Main CFW with BootCTR9 tho.

Example boot_config.ini of that:

[BOOTCTR9]
screenEnabled = 1
screenLog = 0
fileLog = 0
key_delay = 1000
boot_splash = 1
boot_splash_image = /luma/splash.bin
screenBrightness = 0xFF
enableAutosoftboot = 1
enableSoftbootSplash = 0

;Luma3DS (SysNAND)
[DEFAULT]
path = /luma/Luma3DS.firm
delay = 100
enablePathFix = 1

;BrickWait Mode (EmuNAND)
[KEY_DDOWN]
path = /luma/payloads/BrickWait.bin
delay = 100

iirc, you can still access Luma3DS' config and payload chainloader as well.

WAIT, I KNEW I WASN'T THAT CRAZY: BootCTR9+Luma is what's supposed to break extended RAM games, not BootCTR9+Gateway. It was a disclaimer on an old version of Aurora Wright's Luma3DS Wiki. I don't know if it's still an issue on current versions, since I can't find it anywhere now.

 

[Temptress Cerise]

WAIT, I KNEW I WASN'T THAT CRAZY: BootCTR9+Luma is what's supposed to break extended RAM games, not BootCTR9+Gateway. It was a disclaimer on an old version of Aurora Wright's Luma3DS Wiki. I don't know if it's still an issue on current versions, since I can't find it anywhere now.

enablePathFix = 1 - iirc, that fixes that. Pokemon Moon runs just fine on my O3DS, with BootCTR9 as my main .firm file.