Hacking I need a EmuNand

Zane_Julien · Jan 16, 2020

My SD Card is looking like this.

KleinesSinchen · Jan 16, 2020

Eigene Dateien > USB-Speicher 1 > luma > playloads

Is this what you have on the SD? It should be SD:/luma/payloads

Other than that: Are you sure your (Start) button is working?

Zane_Julien · Jan 16, 2020

KleinesSinchen said:
Is this what you have on the SD? It should be SD:/luma/payloads

Other than that: Are you sure your (Start) button is working?

1.: The luma folder is on the root of the sd card.
2.: Why have you marked the "l" in playloads?
3.: Yes, its working normaly. I can confirm in the config menu.

KleinesSinchen · Jan 16, 2020

Zane_Julien said:
2.: Why have you marked the "l" in playloads?

Because it is wrong. It is "payloads" not "playloads"

Zane_Julien · Jan 16, 2020

KleinesSinchen said:
Because it is wrong. It is "payloads" not "playloads"

I don't wanna lie... I just want to KILL myself. I had named it PLAYLOADS everytime, and now, it worked. Thank you!!! I can now acess gm9 and can do the CTRTransfer.

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

Is there an option to close this thread?

KleinesSinchen · Jan 16, 2020

Zane_Julien said:
I don't wanna lie... I just want to KILL myself. I had named it PLAYLOADS everytime, and now, it worked. Thank you!!! I can now acess gm9 and can do the CTRTransfer.

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

Is there an option to close this thread?

Awwww. What a stupid cause of error.
Good luck with troubleshooting the softbrick.

No need to close the thread (only moderators can do this). And maybe you have further questions/problems.

Zane_Julien · Jan 18, 2020

KleinesSinchen said:
No need to close the thread (only moderators can do this). And maybe you have further questions/problems.

Yes, you were right. I transfered the files from the CTRTransfer-Image and tried to boot, but now it says:
An exception occurred
Processor: ARM9
Exception type: prefetch abort (svcBreak)
...
What do I have to do now?

The Real Jdbye · Jan 18, 2020

Zane_Julien said:
I don't wanna lie... I just want to KILL myself. I had named it PLAYLOADS everytime, and now, it worked. Thank you!!! I can now acess gm9 and can do the CTRTransfer.

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

Is there an option to close this thread?

I feel for you man. I make silly mistakes like that in my code sometimes and they can take a whole day to track down, all the while I'm trying every possible thing I can think of while troubleshooting, thinking "this has got to be it", and I'm equally disappointed every time it turns out it didn't help.

run1492 · Jun 23, 2020

KleinesSinchen said:
Sharing NAND dump is against GBAtemp rules!

An emuNAND setup from another console will not work on yours

Take a spare SD and format it with GodMode9 - there are options for various EmuNAND possibilities.

Be prepared for being repeatedly told, that you don't need an EmuNAND.

Yes, we Do Not Need EMUNAND Anymore

... But why ??? Please, I cannot find gooooogling an exhaustive explanation, or a clear answer.

Emunand was used to avoid potentially brick your console and to have a 'second' console for example. Why is it not needed anymore ?

Thanks in advance.

lone_wolf323 · Jun 23, 2020

run1492 said:
Yes, we Do Not Need EMUNAND Anymore

... But why ??? Please, I cannot find gooooogling an exhaustive explanation, or a clear answer.

Emunand was used to avoid potentially brick your console and to have a 'second' console for example. Why is it not needed anymore ?

Thanks in advance.

Bricks are nullified now with NTRboot. There is not much other than a outright fried motherboard where nothing will power on whatsoever that NTRboot cannot fix for bricks. The main point of emunands have become useless to whats gone on with the 3ds scene.

AmandaRose · Jun 23, 2020

The only use emunand has nowadays is for people who have hit the 300 title limit. Create an emunand and you have another 300 spaces. I do question why anyone would have so many games though :rofl2:

KleinesSinchen · Jun 23, 2020

run1492 said:
Yes, we Do Not Need EMUNAND Anymore

... But why ??? Please, I cannot find gooooogling an exhaustive explanation, or a clear answer.

Emunand was used to avoid potentially brick your console and to have a 'second' console for example. Why is it not needed anymore ?

Thanks in advance.

Booting CFW by using an exploit after starting the main operating system requires the main OS to be intact. CFW allows full system control and therefore modifying important data. This could make booting impossible. No boot, no CFW, no access to repair tools → BRICK… and EmuNAND prevented this.

Since A9LH and even more since B9S this is not a problem anymore. Full system control is gained milliseconds after turning on the console and booting into GodMode9 should be possible any time. You can overwrite the complete CTRNAND partition with garbage data and still boot into GodMode9 to restore a NAND image (and even repair the firmware in case no backup exists – though you should have a backup!)
Luma3DS protects B9S from being overwritten. B9S should survive almost any scenario (you have to do VERY stupid things or uninstall on purpose to loose B9S).
And like already mentioned: There is ntrboot allowing to revive a 3DS even in case the complete NAND is overwritten with garbage.

EmuNAND adds complexity and limits (DSiWare does not work from EmuNAND if I remember that correctly). SD cards are more likely to corrupt or fail than the NAND chip. Switching back and forth in between EmuNAND and SysNAND with different titles installed can make Home Menu go nuts, rewrap all software… not worth it if you are not doing tests.

I've done some really mad things with my test console, including trashing SysNAND and EmuNAND and would still never even consider using EmuNAND on a 2|3DS used for gaming.

Hope this helps.

Have fun!

BaamAlex · Jun 23, 2020

run1492 said:
Emunand was used to avoid potentially brick your console and to have a 'second' console for example.

Back then, the Emunand was meant to be, so that people with a low firmware version (but certainly with updated Emunand) could use the eShop. Because, the 3DS has to be on the current firmware to get into the eShop. So that the Sysnand remains on a low firmware (at that time 4.5.0 or so) so that the gateway flash card can still be used. That is why Emunand has been implemented. That's my level of knowledge. Correct me if i'm wrong. And by the way my friend, as long as you don't delete critical systemfiles, you can't theoretically brick your 3ds

The Real Jdbye · Jun 23, 2020

lone_wolf323 said:
Bricks are nullified now with NTRboot. There is not much other than a outright fried motherboard where nothing will power on whatsoever that NTRboot cannot fix for bricks. The main point of emunands have become useless to whats gone on with the 3ds scene.

ntrboot is not a good example since it requires extra hardware, if that was the only way to unbrick without an emuNAND then most people would still be using emuNANDs. @KleinesSinchen 's answer is more correct.

run1492 · Jun 24, 2020

KleinesSinchen said:
Booting CFW by using an exploit after starting the main operating system requires the main OS to be intact. CFW allows full system control and therefore modifying important data. This could make booting impossible. No boot, no CFW, no access to repair tools → BRICK… and EmuNAND prevented this.

Since A9LH and even more since B9S this is not a problem anymore. Full system control is gained milliseconds after turning on the console and booting into GodMode9 should be possible any time. You can overwrite the complete CTRNAND partition with garbage data and still boot into GodMode9 to restore a NAND image (and even repair the firmware in case no backup exists – though you should have a backup!)
Luma3DS protects B9S from being overwritten. B9S should survive almost any scenario (you have to do VERY stupid things or uninstall on purpose to loose B9S).
And like already mentioned: There is ntrboot allowing to revive a 3DS even in case the complete NAND is overwritten with garbage.

EmuNAND adds complexity and limits (DSiWare does not work from EmuNAND if I remember that correctly). SD cards are more likely to corrupt or fail than the NAND chip. Switching back and forth in between EmuNAND and SysNAND with different titles installed can make Home Menu go nuts, rewrap all software… not worth it if you are not doing tests.

I've done some really mad things with my test console, including trashing SysNAND and EmuNAND and would still never even consider using EmuNAND on a 2|3DS used for gaming.

Hope this helps.

Have fun!

Excellent Explanations ! Thank you very much... I cannot thank you every answer here, but let this answer serve for all of you gurus !

It's a relief not having to make an emunand after all the work customfirmwarizing my 'new' second-hand awesomely preserved 3DS XL.

By the way... very funny the portion of the hacking where chinese app is used (video is in spanish, sorry for that):

Greetings !

BaamAlex · Jun 24, 2020

run1492 said:
Excellent Explanations ! Thank you very much... I cannot thank you every answer here, but let this answer serve for all of you gurus !

It's a relief not having to make an emunand after all the work customfirmwarizing my 'new' second-hand awesomely preserved 3DS XL.

By the way... very funny the portion of the hacking where chinese app is used (video is in spanish, sorry for that):

Greetings !

Don't follow a video. They are really quick outdated. Use this.

run1492 · Jun 24, 2020

BaamAlex said:
Don't follow a video. They are really quick outdated. Use this.

Thanks! I've bookmarked that. Anyway, the video worked at 90%, only a few webpages required were unavailable, but searching a little I'd found others to replace the missing ones.

TurdPooCharger · Jun 24, 2020

run1492 said:
Thanks! I've bookmarked that. Anyway, the video worked at 90%, only a few webpages required were unavailable, but searching a little I'd found others to replace the missing ones.

Here's why following video tutorials when installing custom firmware is a bad idea.

New3dsXL boot problem [post #21]

If you visit the Nintendo Homebrew Discord and told people there you followed sthetix's videos, you would be scolded by them with the .vguides command.

「 Kurisu 」 said:
Why you should not use video guides

Reasons to not use video guides:
- They get outdated quickly
- Tough to update and give assistance for
- Can be misinformative and dangerous for the console

Recommended Solution
Read a trusted written tutorial. Try .guide for a list.

Hacking I need a EmuNand

Well-Known Member

GBAtemp's Backup Reminder + Fearless Testing Sina

Well-Known Member

GBAtemp's Backup Reminder + Fearless Testing Sina

Well-Known Member

GBAtemp's Backup Reminder + Fearless Testing Sina

Well-Known Member

*is birb*

Active Member

Well-Known Member

Do what I do. Hold tight and pretend it’s a plan

GBAtemp's Backup Reminder + Fearless Testing Sina

UDE GA NARU ZE!

*is birb*

Active Member

UDE GA NARU ZE!

Active Member

Meh.

Similar threads

Popular threads in this forum

is birb

is birb