Hacking My New Nintendo 3DS only boots up to GodMode9. Help?

kaibsters

Member
Newcomer
Joined
Jul 24, 2020
Messages
9
Trophies
0
Age
19
Location
Virginia, USA
XP
22
Country
United States
When I take the Micro SD out of my New Nintendo 3DS, it only boots up to GodMode9. I cannot get out of it, go to the home menu, or even reboot. Once the Micro SD is inserted however, it's just a black screen.

I feel like I have completely bricked my console. Is there any way I could receive assistance on this problem?
 

kaibsters

Member
Newcomer
Joined
Jul 24, 2020
Messages
9
Trophies
0
Age
19
Location
Virginia, USA
XP
22
Country
United States
Another thing..

I tried to copy over the contents from my working 2DS build, and it also booted up with a black screen. Once I remove the micro SD however, it's back to GodMode9.
 

Shadow#1

Wii, 3DS Softmod & Dumpster Diving Expert
Member
Joined
Nov 21, 2005
Messages
10,451
Trophies
1
XP
6,000
Country
United States
When I take the Micro SD out of my New Nintendo 3DS, it only boots up to GodMode9. I cannot get out of it, go to the home menu, or even reboot. Once the Micro SD is inserted however, it's just a black screen.

I feel like I have completely bricked my console. Is there any way I could receive assistance on this problem?
Nah u just named gm9 as boot.firm on the root of nand and SD card has no luma3ds boot.firm on root
 

lone_wolf323

Well-Known Member
Member
Joined
May 27, 2011
Messages
4,310
Trophies
1
XP
3,338
Country
Canada
When I take the Micro SD out of my New Nintendo 3DS, it only boots up to GodMode9. I cannot get out of it, go to the home menu, or even reboot. Once the Micro SD is inserted however, it's just a black screen.

I feel like I have completely bricked my console. Is there any way I could receive assistance on this problem?
heh. wrong use of bricked, thats for sure. You want lumas boot.firm on the sd card root. https://github.com/LumaTeam/Luma3DS/releases/tag/v10.2
 

kaibsters

Member
Newcomer
Joined
Jul 24, 2020
Messages
9
Trophies
0
Age
19
Location
Virginia, USA
XP
22
Country
United States
Wow, thank you so much! Problem is, it seems my apps from my 2DS didn't transfer over. Do I have to redo the process once again on my New Nintendo 3DS?
 

KleinesSinchen

GBAtemp's Backup Reminder + Fearless Testing Sina
Member
GBAtemp Patron
Joined
Mar 28, 2018
Messages
2,447
Trophies
0
XP
5,239
Country
Germany
Basically everything that was in the guide didn't carry over. Do I just delete and reinstall the cias and such?

Edit: Homebrew Launcher is also gone.
For System Transfer involving non-legit titles see this thread.

When I take the Micro SD out of my New Nintendo 3DS, it only boots up to GodMode9. I cannot get out of it, go to the home menu, or even reboot. Once the Micro SD is inserted however, it's just a black screen.

I feel like I have completely bricked my console. Is there any way I could receive assistance on this problem?
When following the guide this should not happen. The script should copy the Luma and GodMode9 version from SD to CTRNAND. You copied boot.firm (renamed GodMode9.firm) manually to CTRNAND or had GodMode9 as boot file on SD when using the script:
https://3ds.hacks.guide/finalizing-setup#section-vi---ctrnand-luma3ds

If you have any further questions or problems just ask again.

Good luck and have fun!
 

kaibsters

Member
Newcomer
Joined
Jul 24, 2020
Messages
9
Trophies
0
Age
19
Location
Virginia, USA
XP
22
Country
United States
It seems I can't do the system transfer, since my 2DS screen is currently screwed up. I shall instead just restart the steps, so I can get a clean SD and system.

EDIT: Nevermind. Clearing out the SD card doesn't help, since GodMode still boots up regardless.
 
Last edited by kaibsters,

lone_wolf323

Well-Known Member
Member
Joined
May 27, 2011
Messages
4,310
Trophies
1
XP
3,338
Country
Canada
It seems I can't do the system transfer, since my 2DS screen is currently screwed up. I shall instead just restart the steps, so I can get a clean SD and system.

EDIT: Nevermind. Clearing out the SD card doesn't help, since GodMode still boots up regardless.
So.....uhm..... have you read a damned thing anyone has said to you here? Or has it all be completely ignored?
 

kaibsters

Member
Newcomer
Joined
Jul 24, 2020
Messages
9
Trophies
0
Age
19
Location
Virginia, USA
XP
22
Country
United States
No, I have. Most of the solutions listed have not worked (cias don't appear, and etc.). As I'm planning a full reinstall for the Homebrew setup, is it fine if I keep the Luna boot.firm file in the root when I redo Homebrew? The 3DS won't boot up normally without it.

By the way, Kleines specifically said it was alright to ask further questions if I needed assistance. Totally a slow learner, so I understand if your patience is gone for me.
 
Last edited by kaibsters,

Maq47

Developer
Member
Joined
Jan 7, 2012
Messages
1,016
Trophies
1
XP
2,011
Country
United States
No, I have. Most of the solutions listed have not worked (cias don't appear, and etc.). As I'm planning a full reinstall for the Homebrew setup, is it fine if I keep the Luna boot.firm file in the root when I redo Homebrew? The 3DS won't boot up normally without it.
SD card contents are encrypted per-system, so moving your 2DS' SD card contents to your n3DS's microSD card won't make your 2DS' .cia's appear on your n3DS (I assume that this is what you meant).

In your case, put luma's boot.firm on your microSD root, and in luma/payloads/, put GodMode9.firm. Follow this guide to remove CFW completely. Once done, install CFW again following the guide EXACTLY. Whoever originally installed CFW on your n3DS the first time did it wrong.
 

KleinesSinchen

GBAtemp's Backup Reminder + Fearless Testing Sina
Member
GBAtemp Patron
Joined
Mar 28, 2018
Messages
2,447
Trophies
0
XP
5,239
Country
Germany
No, I have. Most of the solutions listed have not worked (cias don't appear, and etc.). As I'm planning a full reinstall for the Homebrew setup, is it fine if I keep the Luna boot.firm file in the root when I redo Homebrew? The 3DS won't boot up normally without it.
A 3DS that boot into GodMode9 already has B9S. No need to start from the beginning. Just do the finalizing setup.
https://3ds.hacks.guide/finalizing-setup

Make sure you have boot.firm (Luma3DS) and boot.3dsx (Homebrew Launcher) in the root directory of your SD.
It seems I can't do the system transfer, since my 2DS screen is currently screwed up. I shall instead just restart the steps, so I can get a clean SD and system.

EDIT: Nevermind. Clearing out the SD card doesn't help, since GodMode still boots up regardless.
Please don't try the "Let's delete everything"-method. That makes things worse. When turning on a 3DS with B9S it does something like this:
Try loading SD:/boot.firm
If this fails
Try loading CTRNAND:/boot.firm
If this also fails
turn off power.

If you follow the finalizing part to the letter and have all files correctly on the SD the console should boot normally without SD afterwards.

SD card contents are encrypted per-system, so moving your 2DS' SD card contents to your n3DS's microSD card won't make your 2DS' .cia's appear on your n3DS (I assume that this is what you meant).

In your case, put luma's boot.firm on your microSD root, and in luma/payloads/, put GodMode9.firm. Follow this guide to remove CFW completely. Once done, install CFW again following the guide EXACTLY. Whoever originally installed CFW on your n3DS the first time did it wrong.
No. Just no. Uninstall CFW, start from scratch, start over… or however this is called is never a good idea.
 
Last edited by KleinesSinchen,

Maq47

Developer
Member
Joined
Jan 7, 2012
Messages
1,016
Trophies
1
XP
2,011
Country
United States
A 3DS that boot into GodMode9 already has B9S. No need to start from the beginning. Just do the finalizing setup.
https://3ds.hacks.guide/finalizing-setup

Make sure you have boot.firm (Luma3DS) and boot.3dsx (Homebrew Launcher) in the root directory of your SD.

Please don't try the "Let's delete everything"-method. That makes things worse. When turning on a 3DS with B9S it does something like this:
Try loading SD:/boot.firm
If this fails
Try loading CTRNAND:/boot.firm
If this also fails
turn off power.

If you follow the finalizing part to the letter and have all files correctly on the SD the console should boot normally without SD afterwards.


No. Just no. Uninstall CFW, start from scratch, start over… or however this is called is never a good idea.
The boot.firm that is on CTRNAND isn't Luma. The only noob-proof way to fix it is to just reinstall.

Edit: I'm trying to noob-proof the process, since he managed to fail following the Guide the first time, which he shouldn't have.
 
Last edited by Maq47,

kaibsters

Member
Newcomer
Joined
Jul 24, 2020
Messages
9
Trophies
0
Age
19
Location
Virginia, USA
XP
22
Country
United States
It worked on the 2DS (until it broke), and somehow failed on the New Nintendo 3DS. Either way, I still screwed it up and will try my best to get this up and running again.
 

KleinesSinchen

GBAtemp's Backup Reminder + Fearless Testing Sina
Member
GBAtemp Patron
Joined
Mar 28, 2018
Messages
2,447
Trophies
0
XP
5,239
Country
Germany
The boot.firm that is on CTRNAND isn't Luma. The only noob-proof way to fix it is to just reinstall.
I still don't recommend doing this. Overwriting boot.firm (GodMode9 renamed) with the correct boot.firm (latest Luma3DS) on CTRNAND is sufficient.

A console in an unknown state may show strange behaviour after uninstalling B9S and the Seedminer way of reinstalling it might be blocked. Too much bad things have happened with the "Let's delete everything" method. Uninstalling B9S is like closing the door an throwing away the key. Or like @Quantumcat once said: "Throwing away the spare tyre because you got a flat."
 

Maq47

Developer
Member
Joined
Jan 7, 2012
Messages
1,016
Trophies
1
XP
2,011
Country
United States
I still don't recommend doing this. Overwriting boot.firm (GodMode9 renamed) with the correct boot.firm (latest Luma3DS) on CTRNAND is sufficient.

A console in an unknown state may show strange behaviour after uninstalling B9S and the Seedminer way of reinstalling it might be blocked. Too much bad things have happened with the "Let's delete everything" method. Uninstalling B9S is like closing the door an throwing away the key. Or like @Quantumcat once said: "Throwing away the spare tyre because you got a flat."
I'm pretty sure that the GM9 'Luma3DS to CTRNAND' script doesn't allow overwriting, so he needs specific instructions to manually modify the boot.firm located there, which I don't think exist online currently. I've never had to remove CFW from a 3DS before, so I didn't know that seedminer could be 'blocked' by removing b9s. Huh.
 

Maq47

Developer
Member
Joined
Jan 7, 2012
Messages
1,016
Trophies
1
XP
2,011
Country
United States
Hang on... Luma Updater also updates the boot.firm on CTRNAND, so if he can access the Homebrew Launcher, he can fix it. @KleinesSinchen, does your n3DS boot at all with the latest Luma boot.firm on your SD root? If not, then we cannot help you fix it. If you can get your n3DS to boot, make sure that there is a working Wi-Fi connection setup on it, and if there is, follow these steps:

Put the Homebrew Launcher's boot.3dsx on your microSD root with Luma's boot.firm, create a '3ds' folder on your microSD root if it doesn't exist, download the latest release of Luma Updater from its GitHub page, copy the .3dsx file to the /3ds/ folder, boot your n3DS, open Health & Safety, press the L + Down (on dpad) + Select buttons to enter the Rosalina menu, go to 'Miscellaneous options > Switch the hb. title to the current app', then close and reopen H&S. Choose Luma Updater from the homebrew list, and use it to update both the microSD card's boot.firm AND the CTRNAND's boot.firm. This SHOULD fix your problems.
 

KleinesSinchen

GBAtemp's Backup Reminder + Fearless Testing Sina
Member
GBAtemp Patron
Joined
Mar 28, 2018
Messages
2,447
Trophies
0
XP
5,239
Country
Germany
Hang on... Luma Updater also updates the boot.firm on CTRNAND, so if he can access the Homebrew Launcher, he can fix it. @KleinesSinchen, does your n3DS boot at all with the latest Luma boot.firm on your SD root? If not, then we cannot help you fix it. If you can get your n3DS to boot, make sure that there is a working Wi-Fi connection setup on it, and if there is, follow these steps:

Put the Homebrew Launcher's boot.3dsx on your microSD root with Luma's boot.firm, create a '3ds' folder on your microSD root if it doesn't exist, download the latest release of Luma Updater from its GitHub page, copy the .3dsx file to the /3ds/ folder, boot your n3DS, open Health & Safety, press the L + Down (on dpad) + Select buttons to enter the Rosalina menu, go to 'Miscellaneous options > Switch the hb. title to the current app', then close and reopen H&S. Choose Luma Updater from the homebrew list, and use it to update both the microSD card's boot.firm AND the CTRNAND's boot.firm. This SHOULD fix your problems.
This is so confusing and getting slightly off-topic.

As I understood the starting point the 3DS does read boot.firm from SD (if present) – the "cleaning" SD might already have caused additional confusion here. "Setup Luma3DS to CTRNAND"-script does overwrite previous files (else any v9.0 Luma3DS version on CTRNAND would also not be replaced on update).
But I will stop here for now.

==============
@kaibsters Just put boot.firm and boot.3dsx [Version 10.2] on your SD and try the finalizing setup (with all the files mentioned there). If this fails we can still try "individual support".

Good luck!
 

kaibsters

Member
Newcomer
Joined
Jul 24, 2020
Messages
9
Trophies
0
Age
19
Location
Virginia, USA
XP
22
Country
United States
Hang on... Luma Updater also updates the boot.firm on CTRNAND, so if he can access the Homebrew Launcher, he can fix it. @KleinesSinchen, does your n3DS boot at all with the latest Luma boot.firm on your SD root? If not, then we cannot help you fix it. If you can get your n3DS to boot, make sure that there is a working Wi-Fi connection setup on it, and if there is, follow these steps:

Put the Homebrew Launcher's boot.3dsx on your microSD root with Luma's boot.firm, create a '3ds' folder on your microSD root if it doesn't exist, download the latest release of Luma Updater from its GitHub page, copy the .3dsx file to the /3ds/ folder, boot your n3DS, open Health & Safety, press the L + Down (on dpad) + Select buttons to enter the Rosalina menu, go to 'Miscellaneous options > Switch the hb. title to the current app', then close and reopen H&S. Choose Luma Updater from the homebrew list, and use it to update both the microSD card's boot.firm AND the CTRNAND's boot.firm. This SHOULD fix your problems.

EDIT: Disregard that completely. I found it, lol.
 
Last edited by kaibsters,

Site & Scene News

General chit-chat
Help Users
  • No one is chatting at the moment.
    Psionic Roshambo @ Psionic Roshambo: https://imgur.com/gallery/BgHrJPC