Homebrew Need help with luma emunand

[izy]

Have you tried using actual light when taking photos. Also dafuq on hosting images on Google drive instead of imgur or an attachment


Also if your getting a black screen using b9s then you are literally failing at the basic step of literally copying the files to your sd card.

If you actually read the guide linked it has literal answers to these issues and a solution to stop that happening if you dont have an sd card inserted.

We are now at the stage where you are just plain ignorant which we can tell from this thread and your posts.

Like if you really meant you want to dev on this console you should go back to basics first since your mistakes begin there.

There are no more answers anyone can give you except read the guide


Also you cant get ntrboot without a flashcard so nothing legit.

The closest thing you can get is the card I own an action replay ds but gl with that

 

[TurdPooCharger]

To run custom firmware all the time without actually installing boot9strap to your 3DS system,

1. Buy the shitty but cheap R4iSDHC series flashcart and set this in ntrboot mode.
2. NTRboot launch the system with Luma3DS as the sdmc:/boot.firm.

If you want to get fancier, attach rubber bumpers to the upper panel that align and press down on the (X), (START), and (SELECT) buttons when you it flip closed to sleep mode. That'll make it easier holding just the (POWER) button for up to 10 secs instead of all of them.

Even more insane would be internally installing a custom modchip that's hooked up to the (X)-(START)-(SELECT)-(POWER) buttons, sleep switch, and in-between the ntrboot flashcart's PCB board soldered to the game cart pinouts. Set this up where turning on the 3DS by pressing the (POWER) button once will automatically signal to the modchip to digitally press the button combos, keep the sleep switch active for a short duration, and toggle the game cart over to read the ntrboot flashcart.

Now, I know what all you guys are thinking, and that yes this is a very roundabout stupid way of semi-permanently running custom firmware... without actually installing custom firmware. A scenario where someone would have to do this is if they've fried their NAND chip from a hardmod and have no means of replacing that chip. To salvage their motherboard, this person would have a valid reason using EmuNAND, and because their physical (Sys)NAND chip is dead, you can't install permanent custom firmware (boot9strap).

 

[Deleted User]

Have you tried using actual light when taking photos. Also dafuq on hosting images on Google drive instead of imgur or an attachment


Also if your getting a black screen using b9s then you are literally failing at the basic step of literally copying the files to your sd card.

If you actually read the guide linked it has literal answers to these issues and a solution to stop that happening if you dont have an sd card inserted.

We are now at the stage where you are just plain ignorant which we can tell from this thread and your posts.

Like if you really meant you want to dev on this console you should go back to basics first since your mistakes begin there.

There are no more answers anyone can give you except read the guide


Also you cant get ntrboot without a flashcard so nothing legit.

The closest thing you can get is the card I own an action replay ds but gl with that

I was lazy and used my O3DSXL to take pictures of my N2DSXL. sry.

 

[Deleted User]

Have you tried using actual light when taking photos. Also dafuq on hosting images on Google drive instead of imgur or an attachment


Also if your getting a black screen using b9s then you are literally failing at the basic step of literally copying the files to your sd card.

If you actually read the guide linked it has literal answers to these issues and a solution to stop that happening if you dont have an sd card inserted.

We are now at the stage where you are just plain ignorant which we can tell from this thread and your posts.

Like if you really meant you want to dev on this console you should go back to basics first since your mistakes begin there.

There are no more answers anyone can give you except read the guide


Also you cant get ntrboot without a flashcard so nothing legit.

The closest thing you can get is the card I own an action replay ds but gl with that

Black screen at rxtools 3dsx, not b9s.

 

[KleinesSinchen]

To run custom firmware all the time without actually installing boot9strap to your 3DS system,

1. Buy the shitty but cheap R4iSDHC series flashcart and set this in ntrboot mode.
2. NTRboot launch the system with Luma3DS as the sdmc:/boot.firm.

[…]

Did you successfully do this? As already mentioned, I can't get it to work.


Test:

• Set Luma3DS to autoboot EmuNAND → Works, shows "Emu" in System Settings each time booting without holding any buttons.
  
• Then I accidentally¹ ran the Un-install Hax script
  • 3DS boots normally, installed non-legit titles: "The software title could not be launched… blabla"
  • Fastboot3DS and Luma are gone… Oh no! What mad person did that?!

---

1. ntrboot
   • boots into SysNAND without loading CFW.
2. ntrboot releasing all buttons and pressing (Select) again
   • Luma3DS v.10.0.1 configuration… Booted from SD via B9S (ntrboot)
   • No settings changed, still autoboot EmuNAND
     
   • boots into SysNAND without loading CFW.
3. ntrboot releasing all buttons and pressing (Select) again
   • removed "Autoboot EmuNAND"
   • boots into SysNAND with Luma loaded.

Especially for the case you mentioned (bad NAND chip) this would be a nice workaround for the future.





____________________
¹ "Accidentally" seems to be very popular on the forum lately – instead of saying "I did something bad or stupid."

 

[TurdPooCharger]

Did you successfully do this? As already mentioned, I can't get it to work.


Test:

• Set Luma3DS to autoboot EmuNAND → Works, shows "Emu" in System Settings each time booting without holding any buttons.
  
• Then I accidentally¹ ran the Un-install Hax script
  • 3DS boots normally, installed non-legit titles: "The software title could not be launched… blabla"
  • Fastboot3DS and Luma are gone… Oh no! What mad person did that?!

---

1. ntrboot
   • boots into SysNAND without loading CFW.
2. ntrboot releasing all buttons and pressing (Select) again
   • Luma3DS v.10.0.1 configuration… Booted from SD via B9S (ntrboot)
   • No settings changed, still autoboot EmuNAND
     
   • boots into SysNAND without loading CFW.
3. ntrboot releasing all buttons and pressing (Select) again
   • removed "Autoboot EmuNAND"
   • boots into SysNAND with Luma loaded.

Especially for the case you mentioned (bad NAND chip) this would be a nice workaround for the future.


____________________
¹ "Accidentally" seems to be very popular on the forum lately – instead of saying "I did something bad or stupid."

I installed the .firm extracted from 1:/title/00040138/20000002 to both FIRM0/1, so no more boot9strap installed. Luma3DS v9.1 works on my n3DSXL as the sdmc:/boot.firm with ntrboot. Maybe it's different for luma v10.0.1.

Edit 1 - Oh, do you mean run EmuNAND from ntrboot launch? Yah, I've done this before by fully bricking my SysNAND by force reflashing a completely garbage nand.bin image. I did this to figure out ways to improve CTRTransfer (Type D9) for bootrom 8046 softbricks. ← DON'T DO WHAT I DID!!!

Basically, install EmuNAND to the SD card with 3DS Multi EmuNAND Creator, do ntrboot with luma as boot.firm, make sure to hold (SELECT) to get to luma configuration, and then set it (X) Autoboot EmuNAND. If that option isn't turn on, luma will try to use nonexistent SysNAND.

Edit 2 - Confirmed Luma3DS v10.0.1 will work as ntrboot's boot.firm.

Update Feb-02-20, Edit 3 - Some of the information in Edit 1 is incorrect. See the explain in the below post #59.

 

[KleinesSinchen]

Basically, install EmuNAND to the SD card with 3DS Multi EmuNAND Creator, do ntrboot with luma as boot.firm, make sure to hold (SELECT) to get to luma configuration, and then set it (X) Autoboot EmuNAND. If that option isn't turn on, luma will try to use nonexistent SysNAND.

I really can't get it to work. Same result with Multi EmuNAND Creator on a different SD (used GodMode9 for formatting before). Loading EmuNAND while Fastboot3DS is installed works. Starting from ntrboot into EmuNAND not (still loads SysNAND without Luma). Ntrboot into EmuNAND also failed on a completely unmodified N3DS (which is the closest to the situation OP has).

I've no trouble ntr-booting any Luma3DS version with SysNAND on any console. Maybe I'm doing it wrong. But it's not important after all. If it works for you this is enough as proof of concept.

Yah, I've done this before by fully bricking my SysNAND by force reflashing a completely garbage nand.bin image. I did this to figure out ways to improve CTRTransfer (Type D9) for bootrom 8046 softbricks. ← DON'T DO WHAT I DID!!!

You should have counted the write cycles on that chip. I guess you will be the first person to wear down the flash memory. My damaged test console has about 15 full write cycles from the "Luma 10 gives black screens on firmware 4.x" tests.
I've said to you in the past that you are abusing your console (in jest). Honestly: The whole community should send you a huge "Thank you!" for everything you have done, tested and developed.

 

[The Real Jdbye]

Thanks, but no. I already tried that and it gives me a black screen and forces me to force reboot my console.
If you want, I can send images of the weird thing pasta cfw does when I try to boot it.

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


I know it's stupid because nobody cares about EmuNand nowdays. Still, would ntrboothax work with a REAL game using save game buffer overflows?

No, because ntrboothax is not actually running in DS mode. It exploits a hidden recovery mode that runs before anything else on the system. A DS flashcart is used to trigger it, but it's actually running in 3DS mode.

Thanks, but no. I already tried that and it gives me a black screen and forces me to force reboot my console.
If you want, I can send images of the weird thing pasta cfw does when I try to boot it.

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


I know it's stupid because nobody cares about EmuNand nowdays. Still, would ntrboothax work with a REAL game using save game buffer overflows?

Pasta CFW does not work on the latest FW or any of the later firmwares neither does rxTools. Both are horribly outdated, obsolete, and in some cases unsafe to use, as they do not have the protections that the far more modern Luma3DS has.
If you really need to hack your console without wifi, then ntrboot is pretty much your only option at this point in the game. If you can go to a friend or family member's house and borrow their wifi connection in order to do http://3ds.hacks.guide it saves you time and money. Although the ntrboot method is somewhat easier, in the time it takes you to order and receive a compatible flashcart, you could have followed the guide many times over.

Why do you insist on wanting to use emuNAND? It seems like no one else has asked you that pretty crucial question. If you explain why we will be better informed to suggest you something that might be a better alternative. But anyway, let me clarify a few things:

• 3DS hacking is very safe when following http://3ds.hacks.guide and as long as you take your time and follow the steps nothing bad can happen to your 3DS. But even if you were to screw up by skipping or forgetting steps, the most that would happen is that you wouldn't be able to proceed with the guide, or you would be missing key components that you might need in the future, your console would still work fine. With all the failchecks in place, and the way the guide has been written and the way the tools used work, there is no way to brick your console by following the guide. You can brick your console by doing stupid stuff like deleting important files in NAND, or uninstalling B9S after having modified important files so that they no longer pass signature checks, but none of that is part of the guide. The general rule is, if you don't know what you're doing, you shouldn't be messing with NAND files or titles manually. As long as you follow that rule, nothing can go wrong, and if you decide you want to mess with NAND files/titles anyway, keep a NAND backup handy in case you need it. This is why emuNAND is pointless nowadays, since B9S loads before most other things in the system, a completely mangled NAND can still be restored with a NAND backup as long as the firm0/firm1 partitions are intact, and Luma3DS prevents these from being modified so in theory, they will always be intact no matter what you do. Even if that somehow fails (which has not happened to this date), ntrboot loads before anything in NAND so it can be used to fix even the worst softbricks. 99.9% of the time you won't need a NAND backup and most softbricks can even be fixed without one. EmuNAND is just the same as keeping a NAND backup on your SD only it has some additional drawbacks, DSiWare won't work from emuNAND for one.
  
• The chance of getting banned from online is pretty much 0% if that's something you care about. The 3DS is dead, and Nintendo are focusing all their efforts on the Switch. Even when the 3DS was current only a small % of CFW users and pirates got banned and almost all were due to playing leaked games online ahead of release, cheating online or in badge arcade, or using .3DS ROMs with public headers on flashcarts like Gateway and Sky3DS+ (this is not a concern with CIAs as they do not contain or need said headers), there have not been any reported bans in a very long time though.
• Modern hacking methods are much safer than trying to get old obsolete CFW like rxTools, Pasta CFW and Gateway 3DS to work, even if you could somehow get them to work (which you won't because they don't work on newer firmwares anyway)

 

[Deleted User]

Could you (somehow) get elevated (arm9) access with ninjhax2 and then load the boot.firm?

 

[lone_wolf323]

Could you (somehow) get elevated (arm9) access with ninjhax2 and then load the boot.firm?

No. Nintendo already patched out the one way there that was a thing years ago.

 

[KleinesSinchen]

Could you (somehow) get elevated (arm9) access with ninjhax2 and then load the boot.firm?

Okay, it gets a little awkward now. No offense intended. This may sound a little harsh/rude… but I mean everything below friendly.

I told you two times:

• There are no public exploits for this on 11.4 and later
  • If there were exploits for ARM9 kernel on newer firmware (like the clever workaround in the 36c3 video) it would not help since:
• Current Luma3DS supports only one method: Loading via B9S (Fastboot3DS does the same but has some more functionality and ntrboot is "one time" B9S)
  • Luma3DS also works when installed directly to FIRM0/1 with "sighax" signature instead of the B9S or Fastboot3DS bootloaders (for the case someone does experiments and installs boot.firm to the FIRM0/1 partitions)

As much as I want to help you, nobody can simply change the facts and adjust reality to you wishes. (Would be really nice).

We told you all possibilities, @The Real Jdbye asked a good question (Why EmuNAND?), and we all told you it is as safe as a software modification on a console can be. Please look at the drama in the Switch section. Or look at messed up CBHC in the Wii U section. Search for Banner bricks in Wii Section combined with "I have no Priiloader, no [email protected] and no NAND backup."

And now, please, compare that to @TurdPooCharger's post above where he told us that he overwrote his complete NAND chip with garbage data and still was able to recover. He even built a script to recover from such a case if the user has no backups.

If you don't accept the limitations, nobody can help you except this guy doing some magic tricks:

Again, please explain:

• Why do you insist on EmuNAND?
• Why do you insist on no permanent modification? (While still wanting all the benefits of the modification)
• What is wrong with getting a $5 flashcart?
• What is wrong with getting a cheap secondary console for the modification and leaving your main devices untouched?

 

[Deleted User]

Okay, it gets a little awkward now. No offense intended. This may sound a little harsh/rude… but I mean everything below friendly.

I told you two times:

• There are no public exploits for this on 11.4 and later
  • If there were exploits for ARM9 kernel on newer firmware (like the clever workaround in the 36c3 video) it would not help since:
• Current Luma3DS supports only one method: Loading via B9S (Fastboot3DS does the same but has some more functionality and ntrboot is "one time" B9S)
  • Luma3DS also works when installed directly to FIRM0/1 with "sighax" signature instead of the B9S or Fastboot3DS bootloaders (for the case someone does experiments and installs boot.firm to the FIRM0/1 partitions)

As much as I want to help you, nobody can simply change the facts and adjust reality to you wishes. (Would be really nice).

We told you all possibilities, @The Real Jdbye asked a good question (Why EmuNAND?), and we all told you it is as safe as a software modification on a console can be. Please look at the drama in the Switch section. Or look at messed up CBHC in the Wii U section. Search for Banner bricks in Wii Section combined with "I have no Priiloader, no [email protected] and no NAND backup."

And now, please, compare that to @TurdPooCharger's post above where he told us that he overwrote his complete NAND chip with garbage data and still was able to recover. He even built a script to recover from such a case if the user has no backups.

If you don't accept the limitations, nobody can help you except this guy doing some magic tricks:

Again, please explain:

• Why do you insist on EmuNAND?
• Why do you insist on no permanent modification? (While still wanting all the benefits of the modification)
• What is wrong with getting a $5 flashcart?
• What is wrong with getting a cheap secondary console for the modification and leaving your main devices untouched?

• Because I only have one modded (luma) 3ds and it's broken.
• So when I get my O3DS (luma) fixed I can use that, but for now do a temp mod on my N2DSXL.
• It will take like a week to deliver, so it's not worth the wait.
• I do, but don't want to use it right now.

 

[KleinesSinchen]

• Because I only have one modded (luma) 3ds and it's broken.
• So when I get my O3DS (luma) fixed I can use that, but for now do a temp mod on my N2DSXL.
• It will take like a week to deliver, so it's not worth the wait.
• I do, but don't want to use it right now.

You've made yourself clear. Your stance on this topic severely limit the possibilities – but I won't question your decisions.

If the O3DS with Luma has software problems you might get help on the forum with that. For hardware damage there are the good guides on ifixit.com

There is nothing more I can add to this topic but a: "Good luck!"

 

[Deleted User]

You've made yourself clear. Your stance on this topic severely limit the possibilities – but I won't question your decisions.

If the O3DS with Luma has software problems you might get help on the forum with that. For hardware damage there are the good guides on ifixit.com

There is nothing more I can add to this topic but a: "Good luck!"

No, my O3DS Won't even boot up. It's a hardware problem.

 

[lone_wolf323]

No, my O3DS Won't even boot up. It's a hardware problem.

How exactly do you presume you are going to get the old 3ds fixed? It could cost as much or sometimes more than just getting a new console.esp when the newer consoles have somewhat better specs than the old ones.

 

[Deleted User]

How exactly do you presume you are going to get the old 3ds fixed? It could cost as much or sometimes more than just getting a new console.esp when the newer consoles have somewhat better specs than the old ones.

I bought it pre-modded with luma and I plan to eventually get it fixed. The battery is dead and the screens don't work. <-- with a temp battery transplant btw.

 

[lone_wolf323]

I bought it pre-modded with luma and I plan to eventually get it fixed. The battery is dead and the screens don't work. <-- with a temp battery transplant btw.

Had you bought the system as it was. or did that happen sometime after you got ahold of the console?

 

[Deleted User]

Had you bought the system as it was. or did that happen sometime after you got ahold of the console?

I bought it in september 2019 and in october 2019 it just broke. I can assume my best bet is to go to an ifixit or something.

 

[TurdPooCharger]

I really can't get it to work. Same result with Multi EmuNAND Creator on a different SD (used GodMode9 for formatting before). Loading EmuNAND while Fastboot3DS is installed works. Starting from ntrboot into EmuNAND not (still loads SysNAND without Luma). Ntrboot into EmuNAND also failed on a completely unmodified N3DS (which is the closest to the situation OP has).

I've no trouble ntr-booting any Luma3DS version with SysNAND on any console. Maybe I'm doing it wrong. But it's not important after all. If it works for you this is enough as proof of concept.

Thanks for bringing this up. You did everything correctly, and it is I who was wrong about being able to boot EmuNAND without a SysNAND. I could have sworn I managed to pull this off before. Maybe I crossed over from an alternative timeline because it feels like I'm experiencing the Mandela Effect about this one.

I went back to check by retrashing my SysNAND with a fully corrupt nand.bin image. This is probably close to the 20th-ish times at this point (lost count since this n3DSXL spends more time softbricked than working).

Every attempt to boot EmuNAND from my spare SD card didn't work. I also tried variations of adding native.firm to sdmc:/luma/sysmodules with (x) Enable loading external FIRMs and modules and (x) Use EmuNAND FIRM if booting with R.

• https://github.com/AuroraWright/Luma3DS/wiki/Optional-features

With the (R)-shoulder button, I can manage to boot with ARM9 error. I also tried EmuNAND with Rei-Six v1.2.1, but this goes straight to turning off the 3DS. It could be due to Rei-Six not being compatible with 11.13 firmware. I'll have to check again later with an older 11.5 nand backup put in as emunand.

***

Updated Info
The minimum requirements to boot EmuNAND are...

• The nand_hdr.bin (NCSD nand header) must be present and valid.
  
• At least one of these FIRM payloads [ boot9strap | fastboot3ds | GodMode9 | Luma3DS ] is installed to either FIRM0 or FIRM1 (only need one).
  • Rei-Six can't be installed or doesn't work.

Except for nand.bin (which is everything), nand_minsize.bin (which is nand.bin without the bonus.bin), and the above two items, everything else listed in the [S:] SYSNAND VIRTUAL could be filled with pure crap values. If you flash in a bad twlmbr.bin (TWL mbr partition table) like in this incident, the 3DS will boot with blue screens and refuse to boot EmuNAND if you use your console's own unique nand_hdr.bin. This can be avoided if you instead use a universal retail nand header as discovered by SciresM's "perfect" sighax signatures.

 

[Deleted User]

Just got an idea.
1. install cfw
2. downgrade to 11.4 or 11.5
3. uninstall cfw to get stock 11.4 or 11.5
4. setup pasta or rxtools