How to resume GodMode9/Luma installation

[Jakso]

I've recently been trying to install Luma3DS and have been following a guide. Somewhere along the way, I missed a step or pressed the wrong button and was unable to continue. Now I need to know how I can resume the installation.

Turning it on without SD card.

Power On+Start, with SD card.

It turns on normally with the SD card.

 

[anotherthing]

I may be totally off base, but it looks like you installed luma to your CTRNAND and it's config.ini has the following setting:

autoboot_mode = dsi

This should be set to "off", but I'm not sure the best way to fix that if it's on the CTRNAND without knowing what else is going on with the system. Of course, I could also be completely off base too.

Also, this page will probably help you:

https://3ds.hacks.guide/checking-for-cfw.html#what-to-do-next

 

[Jakso]

I may be totally off base, but it looks like you installed luma to your CTRNAND and it's config.ini has the following setting:

autoboot_mode = dsi

This should be set to "off", but I'm not sure the best way to fix that if it's on the CTRNAND without knowing what else is going on with the system. Of course, I could also be completely off base too.

Also, this page will probably help you:

I'm checking the files on the SD card, and I'm on this screen.

I'm not sure where to proceed from here.

 

[4d1xlaan]

I may be totally off base, but it looks like you installed luma to your CTRNAND and it's config.ini has the following setting:

autoboot_mode = dsi

This should be set to "off", but I'm not sure the best way to fix that if it's on the CTRNAND without knowing what else is going on with the system. Of course, I could also be completely off base too.

Also, this page will probably help you:

https://3ds.hacks.guide/checking-for-cfw.html#what-to-do-next

it should be possible to at least check the nand in godmode9, /rw/luma/config.ini, godmode should be able to open it as a text file and show what is in it

assuming that the luma installed on nand is recent enough and the config.ini is plain text

 

[Jakso]

I fixed it, for some reason the GodMode9 and Luma3DS zip files I had did not have necessary files. I downloaded them again, and the 3DS is turning on now with the SD card.

However, when I turn it on without the SD card, it still shows this message. Is this normal? If not, how can I fix this?

 

[anotherthing]

However, when I turn it on without the SD card, it still shows this message. Is this normal? If not, how can I fix this?

It's not normal, and that looks like luma is in your CTRNAND and the config.ini is set to autoboot for dsi.

https://wiki.hacks.guide/wiki/3DS:Error_screens/Luma3DS_exception_screen

Under ARM11 exceptions, there's this, which is what you're getting without the SD card:

ns

• The Luma configuration setting Hbmenu autoboot is set to boot to a title that does not exist.
  • To fix, disable the option, install an application with the title ID in sd:/luma/config.ini, or change the set title ID to match an application that does exist.

Ignore where it says "sd:/luma/config.ini" because it's actually on your CTRNAND. You should probably do what @4d1xlaan suggested and use GodMode9 to look at the ini as a text file. I don't think it will edit it, though. Don't delete it, though. Just look to see if it says "autoboot_mode=dsi".

If it does say that, it needs to say "autoboot_mode=off". I'm not sure what the correct way of changing that is when it's in your CTRNAND, though. That's the bridge that can be crossed once we know that's the actual problem.

 

[4d1xlaan]

you can delete the boot.firm and luma folder on nand, they arent used if you boot from sd card, and it should copy boot.firm back to nand at some point anyway. if the folder and config on nand are missing when you boot from nand, it will just create new ones like it does on sd card

 

[lone_wolf323]

you can delete the boot.firm and luma folder on nand, they arent used if you boot from sd card, and it should copy boot.firm back to nand at some point anyway. if the folder and config on nand are missing when you boot from nand, it will just create new ones like it does on sd card

i dont see why it should be said to get rid of those. it creates headaches if the sd card ever craps out.

 

[4d1xlaan]

i dont see why it should be said to get rid of those. it creates headaches if the sd card ever craps out.

I'm not saying to delete them, I'm saying that they can be deleted

reading comprehension is hard

 

[Jakso]

Under ARM11 exceptions, there's this, which is what you're getting without the SD card:

Ignore where it says "sd:/luma/config.ini" because it's actually on your CTRNAND. You should probably do what @4d1xlaan suggested and use GodMode9 to look at the ini as a text file. I don't think it will edit it, though. Don't delete it, though. Just look to see if it says "autoboot_mode=dsi".

If it does say that, it needs to say "autoboot_mode=off". I'm not sure what the correct way of changing that is when it's in your CTRNAND, though. That's the bridge that can be crossed once we know that's the actual problem.

In luma/config.ini, it says:

; Autoboot mode, one of:
; - "off"
; - "3ds": boot into the 3DS title specfied by hbldr_3dsx_titleid
; - "dsi": boot into the DSi title specified by autoboot_dsi_titleid
autoboot_mode = 3ds

 

[anotherthing]

In luma/config.ini, it says:

That's kind of odd. It suggests to me that there might be something wrong with how it installed Luma3DS on the CTRNAND.

@4d1xlaan is correct, and it's probably for the best in this case, that you just delete the boot.firm in the root directory of the CTRNAND as well as the luma directory since there's probably something missing from it anyway.

 

[4d1xlaan]

you should mention what guide it is you were following, because it sounds like it's making you run some kind of script that just copies its own config into nand and you might not want that

a normal install wouldnt have 3ds homebrew autoboot enabled without you knowing, and if you had changed settings on your own I feel like you would remember doing that

unless the guide you followed told you to set those options, but the good guides wouldnt be telling you to do this, so you must have been following some other guide that makes you configure it differently for one way or another

it might even be making you use a modified version of luma, that you have no idea what might be different about it compared to the official one

 

[Jakso]

you should mention what guide it is you were following, because it sounds like it's making you run some kind of script that just copies its own config into nand and you might not want that

a normal install wouldnt have 3ds homebrew autoboot enabled without you knowing, and if you had changed settings on your own I feel like you would remember doing that

unless the guide you followed told you to set those options, but the good guides wouldnt be telling you to do this, so you must have been following some other guide that makes you configure it differently for one way or another

it might even be making you use a modified version of luma, that you have no idea what might be different about it compared to the official one

I followed the guide on 3ds (dot) hacks (dot) guide. I think I got to the part where I input the options for injecting in MSET9-Windows.bat, (pressing 1, 2, 3, or 4) but one of the options did not work, because the .zip files I was using didn't have something necessary. I don't remember what exactly I did, but afaik none of them had anything that was irrelevant for the operation.

That's kind of odd. It suggests to me that there might be something wrong with how it installed Luma3DS on the CTRNAND.

@4d1xlaan is correct, and it's probably for the best in this case, that you just delete the boot.firm in the root directory of the CTRNAND as well as the luma directory since there's probably something missing from it anyway.

Do I do this directly from the 3DS? Will it affect any of my data?

 

[anotherthing]

Do I do this directly from the 3DS? Will it affect any of my data?

No, it'll boot the luma boot.firm from the SD card and use the luma configuration on the SD card. There's obviously a problem with the luma install on your 3DS's CTRNAND.

 

[Jakso]

No, it'll boot the luma boot.firm from the SD card and use the luma configuration on the SD card. There's obviously a problem with the luma install on your 3DS's CTRNAND.

Are there any specific instructions to do this? I got the homebrew channels to work with the SD card.

 

[User154]

In luma/config.ini, it says:

It says autoboot_mode = 3ds and it needs to be off.

Remove sd, press and hold select while turning on to get to the config menu again. Set the hbmenu autoboot to off, save and exit, then reboot and it should boot just fine

 

[Jakso]

It says autoboot_mode = 3ds and it needs to be off.

Remove sd, press and hold select while turning on to get to the config menu again. Set the hbmenu autoboot to off, save and exit, then reboot and it should boot just fine

Ah, I already did that when I was trying to fix it, I don't know why it didn't occur to me to do that again.

It's turning on just fine now. Thanks!

Follow-up question, I had a few Virtual Console games downloaded, and their save is on another SD card. Is there a way to transfer them to the new SD card I'm using?

 

[anotherthing]

Checkpoint should work with Virtual Console titles, but both consoles would need to be hacked for that to work.

 

[Jakso]

Checkpoint should work with Virtual Console titles, but both consoles would need to be hacked for that to work.

I don't have multiple consoles, I have 1 console, and 2 SD cards for it.

 

[anotherthing]

I don't have multiple consoles, I have 1 console, and 2 SD cards for it.

Checkpoint should do it then. It's a utility to back up and restore save files to games. It'll even do cartridge saves.

https://www.gamebrew.org/wiki/Checkpoint_3DS

You can also get it from Universal Updater if I remember correctly.