Hacking Fixing DS mode on a GW-born EmuNAND?

[Searinox]

Okay here goes,

Waaaaaaay back on 4.5, I created an emuNAND with Gateway. That emuNAND has been going through all the updates and is now a 11.2 version. I've only ever launched it with GW mode and as we all know DS mode never worked with Gateway.

But now, I am launching that emuNAND not through Gateway, but rather through Luma 6.6 via A9LH. Although DS mode should work on Luma, whenever I try to go into DS connections or run an NDS title, it hangs on black screen.

Is there anything I can do to unfuck DS mode on it?

 

[Skyshadow101]

-snip-

Install the fresh TWLNAND through the .cia on the troubleshooting section of https://3ds.guide

 

[Searinox]

Thanks but I installed all five modules and still getting black screen hang. Sorry.

EDIT:

I found this post so I removed CtrBootManager9 and booted A9LH directly and it works now! @Hayleia what do you know about custom path? What do I have to do to keep this working with the boot manager? What is this about a path patcher? This is the boot manager I'm using right now.

According to the official documentation:

A9LH version supports binary patch feature. This feature allow to dynamicaly modify the loaded binary. The feature primary usage was for Luma3DS which must internally have its path for GBA and TWL reboot support.

So apparently this is what I am supposed to do. Though I cannot make enough sense of exactly what I'm supposed to do?

EDIT:

I formatted my Luma entry according to this post and now NDS works fine when the emuNAND is booted on Luma through the CTRbootmanager!