Homebrew Updating Rednand\Emunand

[Kubba]

Sorry if this has already been posted, but I keep finding conflicting information.

I have an N3DS with al9h and Cakes, and I want to update to the latest firmware on my emunand.

I've read that all you have to do is update it in system settings, but I've also read that doing that can mess stuff up.

What is the correct procedure?

Thanks ahead of time.

 

[einhuman197]

Switch to Luma3ds. There is no further development for cakes, and changing the cfw only takes 10 minutes or less. With Luma, you can update safely.

 

[Kubba]

Switch to Luma3ds. There is no further development for cakes, and changing the cfw only takes 10 minutes or less. With Luma, you can update safely.

Thanks for the reply!

Is there a guide on how to do this?

 

[xtheman]

Thanks for the reply!

Is there a guide on how to do this?

https://github.com/AuroraWright/Luma3DS/releases
Since your using a9lh just replace your old a9lh.bin with luma3dses. A config will popup and check these optians (Don't check autoboot SYSnand if you want to use emunand)

• “Autoboot SysNAND”
• “Use SysNAND FIRM if booting with R (A9LH)”
• “Show NAND or user string in System Settings”

 

[Kubba]

https://github.com/AuroraWright/Luma3DS/releases
Since your using a9lh just replace your old a9lh.bin with luma3dses. A config will popup and check these optians (Don't check autoboot SYSnand if you want to use emunand)

• “Autoboot SysNAND”
• “Use SysNAND FIRM if booting with R (A9LH)”
• “Show NAND or user string in System Settings”

Thanks again!

So I'm running the Luma CFW now. Before I update, the system settings provide the string, "Sys 10.7.0-32U." All of my CIAs appear on the homescreen, but am I actually updating my Rednand\Emunand?

 

[einhuman197]

You should take out the point autoboot sysnand since you have emunand. Then you can update safely if the settings say emu

 

[Kubba]

You should take out the point autoboot sysnand since you have emunand. Then you can update safely if the settings say emu

Still getting "Sys" string at the setup menu. I know that there are two Nands on the device, with one running 9.2 and the other running 10.7.0. I used the original al9h install method and used Cakes, could there be a file or something that needs replaced?

I'll keep looking for solutions. Thanks!

 

[einhuman197]

You normally don't need files. When you normally start your 3DS without pressing buttons and then open system settings, which version do you get there?

 

[The Catboy]

Although might I suggest if you want something like CakesFW to catch out Corbenik. Corbenik is a CakesFW inspired CFW that shares a lot of similar features to CakesFW.
http://gbatemp.net/threads/corbenik-another-cfw-for-advanced-users-with-bytecode-patches.429612/
Seriously, there's more than just Luma3DS.
http://gbatemp.net/threads/faq-what-cfw-is-best-for-me.428509/#Corbenik

 

[Kubba]

You normally don't need files. When you normally start your 3DS without pressing buttons and then open system settings, which version do you get there?

I have Use Sysnand FIRM and Show Strings checked, and when I press no buttons, I get "Sys 10.7.0-32U". Holding R gives me the same string.

As for the other cfws, I'll certainly look into them after I get this sorted.

Thanks for your replies!

 

[einhuman197]

You should disable sysnand firm. It can occur problems while updating.

 

[Kubba]

You should disable sysnand firm. It can occur problems while updating.

I've tried that too, and it yields the same results. Any idea what could be causing this issue?

 

[einhuman197]

Well that's strange. Anyways, because you have A9lh you could inject you emunand into sysnand. With this setup, you have 1 system for all and you don't have to double install dsiware/gba cias.

 

[Kubba]

So after some lengthy messing around with the N3DS and cfw's, I installed Corbenik to see if it would make a difference. For simplicity's sake, I only have the recommended options and patches enables, as suggested in the Corbenik readme.md.

When I am booting with Use Emunand selected, I get a black screen (I'm using Index 0, which is where my Emunand should be). When I do not have emunand selected, I get the settings version string ".hack//1070:32U". I assume that it is the same NAND that Luma3DS returned in its string.

It seems to me that my new CFWs can't detect or use the Emunand I set up when I used the original Plailect a9lh installation process (the super long and laborious one).

As for injecting emunand into sysnand, I'll look into it if I can't get my emunand to boot with these new CFWs.

Thanks!

Update

I ran EmuNAND9 to check for Emunand or Rednand setups, and it can't detect either. Could it be that I simply don't have an emunand?

 

[Cuphat]

It sounds like you've been running on SysNAND, not EmuNAND. That's not completely surprising, as the A9LH guides for a while have had you restore your former EmuNAND to SysNAND (as there's no benefit to keeping around the old 9.2 SysNAND with A9LH).

You said your version string with Luma was "Sys 10.7.0-32U" which means you were on SysNAND with version 10.7.

Either way, as long as you are using a CFW with FIRM patches (so, Luma in all cases, Cake/Corbenik are fine but require you to enable the FIRM patches IIRC) it is perfectly safe to just update normally.

 

[Kubba]

It sounds like you've been running on SysNAND, not EmuNAND. That's not completely surprising, as the A9LH guides for a while have had you restore your former EmuNAND to SysNAND (as there's no benefit to keeping around the old 9.2 SysNAND with A9LH).

You said your version string with Luma was "Sys 10.7.0-32U" which means you were on SysNAND with version 10.7.

Either way, as long as you are using a CFW with FIRM patches (so, Luma in all cases, Cake/Corbenik are fine but require you to enable the FIRM patches IIRC) it is perfectly safe to just update normally.

Ah. I remember that step in the install now. All this time I was convinced I was running an emunand with some kind of sysnand string as a carryover from the switching of different firmwares. An abundance of caution kept me from updating in the past.

At any rate, I now have the latest firmware from Nintendo, and I have two new CFWs (Luma and Corbenik) to use on my device (I took the time to install the Quick Payload Switcher as well).

Thanks to everyone who contributed for helping me figure this out!