Homebrew Official [Release] EmuNAND9 - Open Source EmuNAND Formatter & Manager

  • Thread starter Thread starter d0k3
  • Start date Start date
  • Views Views 252,807
  • Replies Replies 961
  • Likes Likes 87
So, does this just... not work for anyone else using the Homebrew Launcher? Instead of EmuNAND9 launching properly, the bottom screen flashes red a couple times and I'm booted back to the main menu. What's up with that?
I'm having the same exact problem I've tried using both Browserhax and Menuhax. o3ds downgraded to 9.2 fine but now I can't boot emunand9.
 
Last edited by Bob Dole,
So, does this just... not work for anyone else using the Homebrew Launcher? Instead of EmuNAND9 launching properly, the bottom screen flashes red a couple times and I'm booted back to the main menu. What's up with that?
Well, to my knowledge, it works for everyone :). Are you, by any chance above FW 9.2? Downgraded FWs, I'm not sure about yet.
 
Well, to my knowledge, it works for everyone :). Are you, by any chance above FW 9.2? Downgraded FWs, I'm not sure about yet.
Yeah, I downgraded from 9.9E to 9.2E on an O3DS. I did it after the thing with NATIVE_FIRM was fixed. EmuNAND9 worked once after a lot of attempts, but it's back to red screens once again. I hope I'm not completely screwed...
 
I'm on downgraded 9.2
Yeah, I downgraded from 9.9E to 9.2E on an O3DS. I did it after the thing with NATIVE_FIRM was fixed. EmuNAND9 worked once after a lot of attempts, but it's back to red screens once again. I hope I'm not completely screwed...
That's what I thought... I guess the exploit needed for this does not work on some downgraded NANDs yet. Just to be sure, could you try running MiniPasta from this package? You can make sure it actually works by trying to install something from FBI.
 
That's what I thought... I guess the exploit needed for this does not work on some downgraded NANDs yet. Just to be sure, could you try running MiniPasta from this package? You can make sure it actually works by trying to install something from FBI.
No dice. Unless it's meant to only flash red twice and boot me back to HBL, that is.
 
And then how can I boot into emunand\cfw ?
I strongly suggest you consult one of the guides on that. As a starter... EmuNAND9 tool installs ReiNAND CFW and CakesFW. You need to get some copyrighted files yourself, can't help with that.

No dice. Unless it's meant to only flash red twice and boot me back to HBL, that is.
That's what I thought. EmuNAND is only your first barrier, you will have the same troubles with running CFWs.

The problem you're having there seems to be specific to (improperly? incompletely?) downgraded NANDs. You need to try to solve that.

If you have no idea, check out the Brahma 2 mod (my signature) and try around with the voodoo parameter. Maybe that will work. Use EmuNAND9.bin with that.
 
@mooglazer and @MelonGx , you two first brought up this issue, so I hope you'll help me decide what to do with it. I already contacted @n1ghty via PM and I hope he will be doing an update or release the source code.

If I have to fix EmuNAND9 for compatibility, I have these options...
  1. Use the biggest possible size for EmuNAND (meaning: 1GB for O3DS, 2GB for N3DS), hoping that this will fix it. Big downside: this won't help anyone who already set up his EmuNAND with EmuNAND9.
  2. Do the above, but let the user decide which size to use. Downside: This will be confusing for noobs. Also, won't help anyone who already set it up.
  3. (in addition to the above): Automatically trim / pad NAND backups when injecting. Downside: Less safety, cause the size is an additional factor to check the validity of a NAND backup.
Any ideas? As I said, the problem right now lies in how EmuNAND tool dumps and injects NAND backups (uses the biggest possible size).
 
@mooglazer and @MelonGx , you two first brought up this issue, so I hope you'll help me decide what to do with it. I already contacted @n1ghty via PM and I hope he will be doing an update or release the source code.

If I have to fix EmuNAND9 for compatibility, I have these options...
  1. Use the biggest possible size for EmuNAND (meaning: 1GB for O3DS, 2GB for N3DS), hoping that this will fix it. Big downside: this won't help anyone who already set up his EmuNAND with EmuNAND9.
  2. Do the above, but let the user decide which size to use. Downside: This will be confusing for noobs. Also, won't help anyone who already set it up.
  3. (in addition to the above): Automatically trim / pad NAND backups when injecting. Downside: Less safety, cause the size is an additional factor to check the validity of a NAND backup.
Any ideas? As I said, the problem right now lies in how EmuNAND tool dumps and injects NAND backups (uses the biggest possible size).
I fixed the problem by updating back to 10.3 then RE-downgrading to 9.2, after that emunand9 ran just fine.
 
I fixed the problem by updating back to 10.3 then RE-downgrading to 9.2, after that emunand9 ran just fine.
Most likely you updated really really early (like as soon as memchunkhax2 was finished) and still had the 10.3 NATIVE_FIRM installed... you could have actually run sysupdater without upgrading again and it would probably have worked fine
 
I strongly suggest you consult one of the guides on that. As a starter... EmuNAND9 tool installs ReiNAND CFW and CakesFW. You need to get some copyrighted files yourself, can't help with that.


That's what I thought. EmuNAND is only your first barrier, you will have the same troubles with running CFWs.

The problem you're having there seems to be specific to (improperly? incompletely?) downgraded NANDs. You need to try to solve that.

If you have no idea, check out the Brahma 2 mod (my signature) and try around with the voodoo parameter. Maybe that will work. Use EmuNAND9.bin with that.
Well... I found a solution in a Reddit thread. All that I needed to do was launch it without rxTools. Makes me feel pretty dumb :P
 
  • Like
Reactions: d0k3
Hello! I have a EU N3DS XL with 9.2, I've done the Dump of the SysNAND, but now I want to do the installation of the EmuNAND. But, I don't understand why I need to switch the SD during the process... I can re-insert the same SD? Or is important use another SD? Because my SD has 32gb and I want use this for install RXTool and some .cia!


EDIT: I've alredy copied on my PC the dump of SysNAD (NAND.bin)
 
Last edited by Fenderfix,
Hello! I have a EU N3DS XL with 9.2, I've done the Dump of the SysNAND, but now I want to do the installation of the EmuNAND. But, I don't understand why I need to switch the SD during the process... I can re-insert the same SD? Or is important use another SD? Because my SD has 32gb and I want use this for install RXTool and some .cia!


EDIT: I've alredy copied on my PC the dump of SysNAD (NAND.bin)
You can switch the SD card, you don't have to. You don't have to remove it and put it back in either. That's an option, not a must. Be aware that the SD card set up for EmuNAND will be completely wiped, but I guess you know!
 
Is there anyway to surpass the 16MB limit of the starter.bin in the future? Or the memory of 3DS is fully capped at 16MB?
 
Is there anyway to surpass the 16MB limit of the starter.bin in the future? Or the memory of 3DS is fully capped at 16MB?
To be honest, that limit is (not fully!) arbitrary. There's a lot more memory, but you need to keep in mind that the starter pack is not everything that has to be kept inside of it. Plus ZIP3DSFX (that's the base software behind the self extracting archive) is untested with large archives.

Why would you want more?
 
  • Like
Reactions: tivu100
Having an issue with Emunand : everytime I boot into my 9.5 n3ds emunand w/ rx my 3d gets effed up (top screen gets blurred duplicate-ish when I turn up 3d slider) to fix this I have to put my n3ds in sleep mode by closing screen and reopening. Is there a way to fix this or do I have to close/reopen the screen everytime I boot?

See below...
:blush:
 
Last edited by SterneSchreien,
Having an issue with Emunand : everytime I boot into my 9.5 n3ds emunand w/ rx my 3d gets effed up (top screen gets blurred duplicate-ish when I turn up 3d slider) to fix this I have to put my n3ds in sleep mode by closing screen and reopening. Is there a way to fix this or do I have to close/reopen the screen everytime I boot?
Wrong thread, this is a rxTools issue. But no, there is now way this can be fixed. Everyone has that.
 
  • Like
Reactions: SterneSchreien

Site & Scene News

Popular threads in this forum