Homebrew Unknown problem with luma3ds and godmode9

[Peppe3]

Hey guys,
this happened today with my new 2ds xl. I first modded it 2 weeks ago with seedminer and everything went fine except with a conflict between luma3ds and godmode9 (impotant for later), but other than that everything went smoothly. Fast forward to today my 2ds stops booting up, i go into panic mode but then thought of turning it on without the sd card and godmode9 pops up instead of luma. So now i know that the reason why my 2ds doesn't boot is because of the conflict between luma and godmode, problem is i don't need godmode9, i need luma. So now what am i supposed to do? I think i may have installed godmode9 to ctrnand instead of luma3ds, how do i revert it?

 

[fmkid]

Hey guys,
this happened today with my new 2ds xl. I first modded it 2 weeks ago with seedminer and everything went fine except with a conflict between luma3ds and godmode9 (impotant for later), but other than that everything went smoothly. Fast forward to today my 2ds stops booting up, i go into panic mode but then thought of turning it on without the sd card and godmode9 pops up instead of luma. So now i know that the reason why my 2ds doesn't boot is because of the conflict between luma and godmode, problem is i don't need godmode9, i need luma. So now what am i supposed to do?

It's not a conflict, at all. Possibly you have GodMode9 payload on CTRNAND root as "boot.firm" instead of Luma.

Then, the solution is replace the actual CTRNAND "boot.firm" by that from Luma (using GodMode9):

https://3ds.hacks.guide/finalizing-setup (see the "VI section")

Or, if you want, you can use the Luma Updater app for that (using the option "Set Luma on CTRNAND" or something like that, I don't remember):

https://github.com/KunoichiZ/lumaupdate/releases/latest

 

[Peppe3]

It's not a conflict, at all. Possibly you have GodMode9 payload on CTRNAND root as "boot.firm" instead of Luma.

Then, the solution is replace the actual CTRNAND "boot.firm" by that from Luma (using GodMode9):

https://3ds.hacks.guide/finalizing-setup (see the "VI section")

Or, if you want, you can use the Luma Updater app for that (using the option "Set Luma on CTRNAND" or something like that, I don't remember):

https://github.com/KunoichiZ/lumaupdate/releases/latest

the problem is that as soon as i put the sd card my 2ds won't boot

 

[fmkid]

the problem is that as soon as i put the sd card my 2ds won't boot

Is "boot.firm" from Luma CFW on the root of the console SD card, at least? Your SD card is on FAT32 format?

It could be possibly that the console SD card is on a bad state (corrupted or damaged).

Please check/analyze it, and if it's possible try using quadruple reformatting:

https://gbatemp.net/threads/new-2ds-xl-microsd-card-error.534480/#post-8569741

Or use another clean/FAT32-formatted SD card. And later do this tutorial (entire):

https://3ds.hacks.guide/finalizing-setup

 

[Peppe3]

Is "boot.firm" from Luma CFW on the root of the console SD card, at least? Your SD card is on FAT32 format?

It could be possibly that the console SD card is on a bad state (corrupted or damaged).

Please check/analyze it, and if it's possible try using quadruple reformatting:

https://gbatemp.net/threads/new-2ds-xl-microsd-card-error.534480/#post-8569741

Or use another clean/FAT32-formatted SD card. And later do this tutorial (entire):

https://3ds.hacks.guide/finalizing-setup

ok i managed to run luma3ds by deleting the boot.firm on ctrnand, now the problem is that i want to put luma in ctrnand but godmode9 won't boot when i hold start, nor does the chainloader boot up when i hold start, godmode9 just won't boot in my 2ds unless i rename it to boot.firm and screw up everything again

EDIT: my sd card works, it's in fat32 and has boot.firm in the root, there's just this problem with godmode9

 

[fmkid]

ok i managed to run luma3ds by deleting the boot.firm on ctrnand, now the problem is that i want to put luma in ctrnand but godmode9 won't boot when i hold start, nor does the chainloader boot up when i hold start, godmode9 just won't boot in my 2ds unless i rename it to boot.firm and screw up everything again

EDIT: my sd card works, it's in fat32 and has boot.firm in the root, there's just this problem with godmode9

Do you want to run GodMode9 (throught Luma) from SD card, from CTRNAND, or both?

At the other hand, perharps if you don't know it, there's a well-known issue with GodMode9 launched throught Luma (pressing START button). And the solution is put another .firm payload on "luma/payloads" location:

https://github.com/LumaTeam/Luma3DS/issues/1460

 

[Peppe3]

Do you want to run GodMode9 (throught Luma) from SD card, from CTRNAND, or both?

At the other hand, perharps if you don't know it, there's a well-known issue with GodMode9 launched throught Luma (pressing START button). And the solution is put another .firm payload on "luma/payloads" location:

https://github.com/LumaTeam/Luma3DS/issues/1460

I want to run godmode9 from the SD card.
This issue you're telling me is the same one I have and I did put another payload, but the Luma chainloader still doesn't boot when I hold start, there's just an empty black screen

 

[fmkid]

I want to run godmode9 from the SD card.
This issue you're telling me is the same one I have and I did put another payload, but the Luma chainloader still doesn't boot when I hold start, there's just an empty black screen

Mmmm... Are you sure that you have GodMode9.firm and the another .firm payload inside of "luma/payloads" location on your SD?

Perharps you have the "payloads" folder on another location or with a different name (it shall be "payloads" exactly, not "playloads" or something else)

 

[Peppe3]

Mmmm... Are you sure that you have GodMode9.firm and the another .firm payload inside of "luma/payloads" location on your SD?

Perharps you have the "payloads" folder on another location or with a different name (it shall be "payloads" exactly, not "playloads" or something else)

Yes, I'm sure

 

[fmkid]

Yes, I'm sure

And Luma's "boot.firm" is on the root of your SD?

 

[Peppe3]

And Luma's "boot.firm" is on the root of your SD?

Yes

 

[Lacius]

GodMode9 black screens using the latest Luma3DS as a chainloader. Either put multiple payloads in luma/payloads or use the latest nightly of GodMode9.

The reason for this is a screen init bug.

 

[fmkid]

Yes

It's really weird then! IDK what it is if you have all I said to you in order (apparently)!

My last recommendation would be try using fastboot3ds:

https://github.com/derrekr/fastboot3DS

@Lacius He said he already put another payload on "luma/payloads" location with the GodMode9 one

Edit: @Peppe3 Can you check if when you enter to Luma's config menu (pressing SELECT on boot) it shows "Booted from SD via B9S" or "Booted from CTRNAND via B9S" text?

 

[The Real Jdbye]

I want to run godmode9 from the SD card.
This issue you're telling me is the same one I have and I did put another payload, but the Luma chainloader still doesn't boot when I hold start, there's just an empty black screen

You could just put GodMode9 as boot.firm on the SD card, and change it back when done. That should rule out any issues caused by Luma3DS.

 

[Peppe3]

You could just put GodMode9 as boot.firm on the SD card, and change it back when done. That should rule out any issues caused by Luma3DS.

That's exactly what I did and that's what caused this issue in the first place

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

It's really weird then! IDK what it is if you have all I said to you in order (apparently)!

My last recommendation would be try using fastboot3ds:

https://github.com/derrekr/fastboot3DS

@Lacius He said he already put another payload on "luma/payloads" location with the GodMode9 one

Edit: @Peppe3 Can you check if when you enter to Luma's config menu (pressing SELECT on boot) it shows "Booted from SD via B9S" or "Booted from CTRNAND via B9S" text?

It says booted from SD via b9s

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

Thanks for all the help, the chain loader finally showed up and I managed to boot GodMode9. Thank you so so much you guys are the best

 

[TurdPooCharger]

If issues arise again later like data corruption, game crashing, or titles go missing / black icons on HOME Menu, check if your SD card is fake, faulty, or dying.

1. Copy everything off the SD card to a computer.
2. Quadruple reformat.
3. Full Write + Verify the empty card in H2testw. Do not skip.

 

[The Real Jdbye]

That's exactly what I did and that's what caused this issue in the first place

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


It says booted from SD via b9s

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

Thanks for all the help, the chain loader finally showed up and I managed to boot GodMode9. Thank you so so much you guys are the best

No, you replaced it on NAND, I'm only telling you to replace it on SD.

 

[vinzentg37]

Quick guide if someone has a similar problem: Copy everything from your sd card to a save place on your pc. Format you sd card FAT32, then copy the files back on the card. If this doesn't solve the problem download the latest release of luma3DS and copy the boot.firm to the root of your sd card. Check if there is a folder called "payloads" in the luma folder, if not create one. Delete all present payloads from luma\payloads, download the latest release of Godmode9 and paste the .firm there. Create a empty file called "DO_NOT_LAUNCH.firm". Then put the sd card in your 3ds and press and hold power + start for 2 seconds, this should bring up a menu of luma. Select the Godmode9.firm (highlighted red) and press A. Once in Godmode 9 go to SD (set date and time first when asked to) and copy boot.firm. Press B to go back and select CTRNAND, paste the boot.firm there. (un- and relock writing permissions when asked to). PressB to go back, press home and select "power off". Starting the 3DS again should bring up the luma setup menu and pressing start should launch the home menu. (This instructions should work, but I don't do this stuff on a daily, so please tell me if I made any mistakes here which will cause problems)
Edit: The part with the empty .firm file may seem random, but I experienced some versions of lume which wont launch the .firm if there is only one.