3DS has broken 3D slider and can’t get past setup and play DS games

[Joom]

I just get an error

Alright, it should still be possible to work around this. Put 2DSaver's 3dsx file under the "3ds" directory on your SD, and name it something like "2dsaver.3dsx". After that, place the homebrew launcher's 3dsx on the root of the SD with the name "boot.3dsx". I just tested this myself, so I know the HB loader should at least launch without an error. Once you're in the HB menu, try launching 2DSaver. Since you bought this pre-hacked, it may also be a good idea to ensure you're on the Latest Luma and HB loader versions.

 

[kellylinc08]

Alright, it should still be possible to work around this. Put 2DSaver's 3dsx file under the "3ds" directory on your SD, and name it something like "2dsaver.3dsx". After that, place the homebrew launcher's 3dsx on the root of the SD with the name "boot.3dsx". I just tested this myself, so I know the HB loader should at least launch without an error. Once you're in the HB menu, try launching 2DSaver. Since you bought this pre-hacked, it may also be a good idea to ensure you're on the Latest Luma and HB loader versions.

I did all the steps and updated luma to 13.2.1 and still get the same error

 

[Joom]

I did all the steps and updated luma to 13.2.1 and still get the same error

Even when booting to the homebrew loader menu? Something seems up with your Luma install. Did you copy the settings.ini file from the 2DSaver release to the luma directory on your SD? If so, that might be the cause. It has the loader's title ID set to 2DSaver's, and you'll want to delete that file so Luma can generate a new one.

 

[kellylinc08]

Even when booting to the homebrew loader menu? Something seems up with your Luma install. Did you copy the settings.ini file from the 2DSaver release to the luma directory on your SD? If so, that might be the cause. It has the loader's title ID set to 2DSaver's, and you'll want to delete that file so Luma can generate a new one.

Still won’t work. Can I disable the arm11 handler on 13.2.1? I don’t see the option to do it in the luma menu

Post automatically merged: Nov 3, 2024

Even when booting to the homebrew loader menu? Something seems up with your Luma install. Did you copy the settings.ini file from the 2DSaver release to the luma directory on your SD? If so, that might be the cause. It has the loader's title ID set to 2DSaver's, and you'll want to delete that file so Luma can generate a new one.

 

[Joom]

I don’t see the option to do it in the luma menu

It's in the Rosalina menu. You'll have to open its config file with a text editor, and disable it that way.

 

[kellylinc08]

It's in the Rosalina menu. You'll have to open its config file with a text editor, and disable it that way.

Where is the config file located and what is it called?

Post automatically merged: Nov 3, 2024

It's in the Rosalina menu. You'll have to open its config file with a text editor, and disable it that way.

I found the config file in the luma folder, but it doesn’t match my settings and nothing happens when I edit the disable arm11 handler or other settings like brightness. Is it in the wrong folder?

 

[Joom]

I found the config file in the luma folder, but it doesn’t match my settings and nothing happens when I edit the disable arm11 handler or other settings like brightness. Is it in the wrong folder?

No, that should be the right folder. If you don't use the exact setting it expects, it won't work. Be sure you're not including any extra characters around it. Also, does this file update if you make changes through Luma's menu? I'm kinda wondering if the Luma instance you're booting from is on the NAND, and not the SD.

 

[kellylinc08]

I think it is from the NAND because the config does not change when I change it from the 3DS and it came without an SD card, so the hacks were already on the system. Is there a way to modify it if it’s in the NAND?

No, that should be the right folder. If you don't use the exact setting it expects, it won't work. Be sure you're not including any extra characters around it. Also, does this file update if you make changes through Luma's menu? I'm kinda wondering if the Luma instance you're booting from is on the NAND, and not the SD.

Post automatically merged: Nov 3, 2024

No, that should be the right folder. If you don't use the exact setting it expects, it won't work. Be sure you're not including any extra characters around it. Also, does this file update if you make changes through Luma's menu? I'm kinda wondering if the Luma instance you're booting from is on the NAND, and not the SD.

Wait that could also be why it ignores the homebrew and 2DSaver files

 

[Joom]

Wait that could also be why it ignores the homebrew and 2DSaver files

I share the same thinking. You can move them there using Godmode9, but it'd likely be easier to just put Luma's firm file on the root of the SD. It's supposed to have boot preference when present, and it existing on the NAND is mainly just to keep the console bootable without an SD. That's a caveat of B9S; there must be a boot.firm present somewhere for the console to boot up. It otherwise softbricks. You could even go one step further, and remove Luma from the NAND in order to force it to use the SD, but I'd warn against this in case your SD slot is somehow faulty.

 

[Kwyjor]

I keep forgetting that the CTR Transfer Type D9 script also has the ability to bypass the setup.
https://gbatemp.net/threads/release-godmode9-scripts-megathread.482150/page-9#BYPASS

 

[Joom]

@kellylinc08 I also saw your post over on the Rehid thread. There's no app involved. It's basically a sysmodule patch. Inside its zip are a "luma" and "rehid" directory. You just copy both of these to the root of the SD, and be sure to enable the loading of external firms and modules under Luma's config. To configure Rehid itself, you edit the JSON file that's in its directory on your SD.

 

[kellylinc08]

I share the same thinking. You can move them there using Godmode9, but it'd likely be easier to just put Luma's firm file on the root of the SD. It's supposed to have boot preference when present, and it existing on the NAND is mainly just to keep the console bootable without an SD. That's a caveat of B9S; there must be a boot.firm present somewhere for the console to boot up. It otherwise softbricks. You could even go one step further, and remove Luma from the NAND in order to force it to use the SD, but I'd warn against this in case your SD slot is somehow faulty.

I put luma's firm on the root of the SD card and disabled the arm11 handler, but now it just sends me to a blank screen when I try to turn on the system

Post automatically merged: Nov 4, 2024

I keep forgetting that the CTR Transfer Type D9 script also has the ability to bypass the setup.
https://gbatemp.net/threads/release-godmode9-scripts-megathread.482150/page-9#BYPASS

How do I install it? I don't know what to do with the gm9 file and can’t find instructions

 

[Kwyjor]

How do I install it? I don't know what to do with the gm9 file and can’t find instructions

You run it using Godmode9, just like any other .gm9 script, including the ones you used to initially install CFW.

This script does many different things, but you are solely interested in this bypass functionality.

 

[kellylinc08]

You run it using Godmode9, just like any other .gm9 script, including the ones you used to initially install CFW.

This script does many different things, but you are solely interested in this bypass functionality.

Thank you so much! It worked! Some geniuses on here. Thank you also to Joom for assisting me.

Post automatically merged: Nov 4, 2024

Oh yes thank you to everyone else who helped me as well

 

[4d1xlaan]

I put luma's firm on the root of the SD card and disabled the arm11 handler, but now it just sends me to a blank screen when I try to turn on the system

for future reference, disabling error handler doesn't prevent errors from happening. it just means you're not going to see a message when it errors