Hacking I need a EmuNand

[Zane_Julien]

Hey there,
I have got a little problem with my CFW 3ds. I don´t want to explain it here, I only have one question: Can anyone send me a finished EmuNand for a 3ds?
I´m asking because I´m not able to use the Multinand tool, and I havn´t got any other ideas.

 

[KleinesSinchen]

Hey there,
I have got a little problem with my CFW 3ds. I don´t want to explain it here, I only have one question: Can anyone send me a finished EmuNand for a 3ds?
I´m asking because I´m not able to use the Multinand tool, and I havn´t got any other ideas.

1. Sharing NAND dump is against GBAtemp rules!
2. An emuNAND setup from another console will not work on yours
3. Take a spare SD and format it with GodMode9 - there are options for various EmuNAND possibilities.
4. Be prepared for being repeatedly told, that you don't need an EmuNAND.

 

[duwen]

What?
That's not how it works...
An EmuNand is essentially a clone of YOUR SysNand - someone elses won't work.

 

[DSoryu]

First of all, EmuNAND is exclusive for the console where it was created on, so no matter what, other emunands will NEVER work with your 3DS. Second, emunand is no longer needed, you should follow 3ds.guide, please don't follow outdated tutorials or videos, otherwise you will mess up your console.

 

[Zane_Julien]

1. Sharing NAND dump is against GBAtemp rules!
2. An emuNAND setup from another console will not work on yours
3. Take a spare SD and format it with GodMode9 - there are options for various EmuNAND possibilities.
4. Be prepared for being repeatedly told, that you don't need an EmuNAND.

I can´t use Godmode9, and I can´t boot my 3ds anymore

 

[KleinesSinchen]

I can´t use Godmode9, and I can´t boot my 3ds anymore

Then how exactly are you going to boot an EmuNAND anyway?

• Was happens when you turn on the 3DS?
• What did you do to brick?

All in all: More information please.

 

[BaamAlex]

I can´t use Godmode9, and I can´t boot my 3ds anymore

It doesn't make sense to boot an emunand when you can't boot your 3ds
And how already wrote here, you can't use a emunand from another console.

 

[Zane_Julien]

Then how exactly are you going to boot an EmuNAND anyway?

• Was happens when you turn on the 3DS?
• What did you do to brick?

All in all: More information please.

I have got a N3ds with luma CFW. The boot.firm is installed to FIRM0 and FIRM1. The Luma Chainloader doesn't work. The CTRNand is empty,and when I try to boot, it says:


An error has occurred:
Unable to mount CTRNAND or load the CTRNAND FIRM
.
Please use an external one.
Press any button to shut down.

The Luma Config Menu loads normally when holding SELECT at boot. And I haven't got a Nand Backup.

 

[KleinesSinchen]

Now I remember your case. Should have checked your post history right away.

The facts did not change. You have to boot into GodMode9 in order to do anything. If the chainloader does not work for you this means one or more of these:

• SD defect/incompatible
• missing/wrong file(s)
• wrong filesystem
• SD reader defective/disconnected
• Or something mysterious I don’t know

I did the testing a few weeks ago and found that Luma3DS chainloader works just fine when it is installed into FIRM0/1 (not repeating the test now).

If you still suspect Luma chainloader does not work in your case because it is installed in the FIRM partitions, you can bypass the normal boot procedure with ntrboot. Take a known good, tested and FAT32 formatted SD and put only GodMode9.firm renamed to boot.firm (and the other stuff from the GodMode9 archive) and try starting it with the ntrboot method.

Without an existing NAND-image you are not able to create an EmuNAND.

Once you are able to boot into GodMode9 rebuilding with CTRTransfer Type D9 or – as a last resort Lazarus3DS – becomes a possibility.

 

[Zane_Julien]

"If you still suspect Luma chainloader does not work in your case because it is installed in the FIRM partitions, you can bypass the normal boot procedure with ntrboot. Take a known good, tested and FAT32 formatted SD and put only GodMode9.firm renamed to boot.firm (and the other stuff from the GodMode9 archive) and try starting it with the ntrboot method."
What do I need for ntrboot?

 

[Quantumcat]

"If you still suspect Luma chainloader does not work in your case because it is installed in the FIRM partitions, you can bypass the normal boot procedure with ntrboot. Take a known good, tested and FAT32 formatted SD and put only GodMode9.firm renamed to boot.firm (and the other stuff from the GodMode9 archive) and try starting it with the ntrboot method."
What do I need for ntrboot?

A DS flashcart that is flashed for ntrboot. See https://3ds.guide/installing-boot9strap-(ntrboot) (except you want to use GodMode9 not SafeB9SInstaller)

 

[TurdPooCharger]

@Zane_Julien, turn on the 3DS and hold the (SELECT) button.

What version Luma3DS v#.# configuration does it state?

If you see Luma3DS configuration, which one of these in the bottom list does it say on the lower screen?

• Booted from CTRNAND via B9S
• Booted from CTRNAND via FIRM0
• Booted from CTRNAND via FIRM1
• Booted from SD via B9S
• Booted from SD via FIRM0
• Booted from SD via FIRM1

 

[Zane_Julien]

@Zane_Julien, turn on the 3DS and hold the (SELECT) button.

What version Luma3DS v#.# configuration does it state?

If you see Luma3DS configuration, which one of these in the bottom list does it say on the lower screen?

• Booted from CTRNAND via B9S
• Booted from CTRNAND via FIRM0
• Booted from CTRNAND via FIRM1
• Booted from SD via B9S
• Booted from SD via FIRM0
• Booted from SD via FIRM1

It says Luma v10.1 and Booted from FIRM0 via b9s

 

[TurdPooCharger]

It says Luma v10.1 and Booted from FIRM0 via b9s

This doesn't seem like a valid message. Please be specific the exact Boot from <location> via <entry>. If that's what really states, can you take a picture and post it here?

 

[Zane_Julien]

This doesn't seem like a valid message. Please be specific the exact Boot from <location> via <entry>. If that's what really states, can you take a picture and post it here?

Hm, I don't understand THAT: I put the Godmode9.firm on the root of the SD Card and renamed it to boot.firm, and then booted while holding select, and the luma config menu appears, and it says
Luma3DS v10.0.1 configuration
...
Booted from SD via FIRM0
But when I try to boot without pressing anything, I get the same Error as before.

 

[TurdPooCharger]

Hm, I don't understand THAT: I put the Godmode9.firm on the root of the SD Card and renamed it to boot.firm, and then booted while holding select, and the luma config menu appears, and it says
Luma3DS v10.0.1 configuration
...
Booted from SD via FIRM0
But when I try to boot without pressing anything, I get the same Error as before.

First, you'll need to fix the FIRM0 and FIRM1 partitions by reflashing boot9strap onto them.

1. Download GodMode9 v1.9.1 and place this at:
   • sdmc:/luma/payloads/GodMode9.firm
2. Download boot9strap v1.3 and place these at:
   • sdmc:/boot9strap/boot9strap.firm
   • sdmc:/boot9strap/boot9strap.firm.sha
3. Turn on the 3DS and hold (START) to access Luma3DS chainloader → GodMode9.
4. Go to [0:] SD CARD (NOLABEL)/boot9strap/boot9strap.firm → press (A) → Calculate SHA-256.
   • You want SHA-256: 79C68585B4BA1D7C4A91B858861553E768C6576B92E303810B33219736B3598B
   • If this is not the exact hash, do not continue to step 5.
5. Press (A) on boot9strap.firm → FIRM image options... → Install FIRM → Install to both → button combo → <A> to continue.
6. Turn off the 3DS by press (POWER) → Poweroff system.
   
7. Turn on the 3DS again and hold the (SELECT) button to access Luma3DS v10.0.1 configuration.
8. Verify that the bottom screen says one of these. Either is fine:
   • Booted from CTRNAND via B9S
   • Booted from SD via B9S

***

The 3DS will probably still produce this error when trying to boot HOME Menu.

An error has occurred:

Unable to mount CTRNAND or load the CTRNAND FIRM

Please use an external one.

Press any button to shutdown.

As was previously mentioned in Sinchen's post, you will need to fix the 3DS firmware (which is separate from custom firmware) with either CTRTransfer or CTRTransfer (Type D9).

For more details in how to,

• Help i think my new 3ds is bricked(please help) [post #20]

 

[Zane_Julien]

First, you'll need to fix the FIRM0 and FIRM1 partitions by reflashing boot9strap onto them.

1. Download GodMode9 v1.9.1 and place this at:
   • sdmc:/luma/payloads/GodMode9.firm
2. Download boot9strap v1.3 and place these at:
   • sdmc:/boot9strap/boot9strap.firm
   • sdmc:/boot9strap/boot9strap.firm.sha
3. Turn on the 3DS and hold (START) to access Luma3DS chainloader → GodMode9.
4. Go to [0:] SD CARD (NOLABEL)/boot9strap/boot9strap.firm → press (A) → Calculate SHA-256.
   • You want SHA-256: 79C68585B4BA1D7C4A91B858861553E768C6576B92E303810B33219736B3598B
   • If this is not the exact hash, do not continue to step 5.
5. Press (A) on boot9strap.firm → FIRM image options... → Install FIRM → Install to both → button combo → <A> to continue.
6. Turn off the 3DS by press (POWER) → Poweroff system.
   
7. Turn on the 3DS again and hold the (SELECT) button to access Luma3DS v10.0.1 configuration.
8. Verify that the bottom screen says one of these. Either is fine:
   • Booted from CTRNAND via B9S
   • Booted from SD via B9S

***

The 3DS will probably still produce this error when trying to boot HOME Menu.


As was previously mentioned in Sinchen's post, you will need to fix the 3DS firmware (which is separate from custom firmware) with either CTRTransfer or CTRTransfer (Type D9).

For more details in how to,

• Help i think my new 3ds is bricked(please help) [post #20]

My Problem is that I can't access Luma Chainloader. It just doesn't open when holding start. Because of this, I used Fastboot3DS, but I broke that by installing boot.firm to FIRM0 and FIRM1.

 

[TurdPooCharger]

My Problem is that I can't access Luma Chainloader. It just doesn't open when holding start. Because of this, I used Fastboot3DS, but I broke that by installing boot.firm to FIRM0 and FIRM1.

Keep the GodMode9 v1.9.1 in place and try adding another FIRM payload like GodMode9 v1.7.1 at:

• sdmc:/luma/payloads/GodMode9_v1.7.1.firm (renamed)

There's a bug where GodMode9 v1.9.1 can fail to boot. Yours might be related.

• [BUG] Chainload booting to GM9 v1.9.1 from v1.9.0 or v1.9.1 will black screen.

If Luma3DS chainloader does appear, choose GodMode9 v1.7.1.

***

If you installed fastboot3DS on FIRM0/1, turn on the 3DS and the hold the (HOME) button.

You should see something like this. To chainload boot to GodMode9,

• fastboot3DS → [+] boot from file... → sdmc:/luma/payloads/GodMode9.firm

 

[Zane_Julien]

Keep the GodMode9 v1.9.1 in place and try adding another FIRM payload like GodMode9 v1.7.1 at:

• sdmc:/luma/payloads/GodMode9_v1.7.1.firm (renamed)

There's a bug where GodMode9 v1.9.1 can fail to boot. Yours might be related.

• [BUG] Chainload booting to GM9 v1.9.1 from v1.9.0 or v1.9.1 will black screen.

If Luma3DS chainloader does appear, choose GodMode9 v1.7.1.

***

If you installed fastboot3DS on FIRM0/1, turn on the 3DS and the hold the (HOME) button.

You should see something like this. To chainload boot to GodMode9,

• fastboot3DS → [+] boot from file... → sdmc:/luma/payloads/GodMode9.firm

I will try the gm9 v1.7.1 thing, and I said IFastboot3DS WAS installed to FIRM0, but then I installed boot.firm to FIRM0 and FIRM1 and because of this, Fastboot3DS was deleted. I'll tell you if Godmode9 v1.7.1 worked. Thanks!

 

[Zane_Julien]

Keep the GodMode9 v1.9.1 in place and try adding another FIRM payload like GodMode9 v1.7.1 at:

• sdmc:/luma/payloads/GodMode9_v1.7.1.firm (renamed)

There's a bug where GodMode9 v1.9.1 can fail to boot. Yours might be related.

• [BUG] Chainload booting to GM9 v1.9.1 from v1.9.0 or v1.9.1 will black screen.

If Luma3DS chainloader does appear, choose GodMode9 v1.7.1.

***

If you installed fastboot3DS on FIRM0/1, turn on the 3DS and the hold the (HOME) button.

You should see something like this. To chainload boot to GodMode9,

• fastboot3DS → [+] boot from file... → sdmc:/luma/payloads/GodMode9.firm

The luma chainloader doesn't appear. I've gm9 v1.9.1 and v1.7.1 in gm9sd/luma/playloads and boot while holding start, but I get the same error as everytime.