Hacking An extra step to update your EmuNAND firmware safely

[mznova]

I heard some people accidentally updated their real Nand because accepting the nintendo agreements kicked them out of Emunand without them knowing. I just thought I'd share this method to more safely update your emuNAND since I thought of it and it worked for me. This method is only meant to provide an extra layer of protection. Obviously common sense and the ability to read the original instructions still apply.

-Before you go into settings to update your GW3D firmware, make sure you are sitting next to your wireless router.
-Check to make sure 100% that you are in GW3D firmware.
-Proceed to update your firmware (Be sure NOT to exit out of settings).
-Accept the agreement and when you see the download dialog with the blue progress bar, disconnect the power to your router.
-Wait until your 3DS gives you a firmware update failed error and kicks you back to the home screen
-You should be in the real NAND again with the old untouched firmware.
(Neither firmware should have been touched)

These steps are a protection to make sure that you have gone through all the possible agreements/hiccups the could possibly kick you from EmuNAND back to real NAND. Now that you are 100% sure you can reach the download screen without any problems, you should be safe from being kicked by any agreement dialogs back to real NAND.

Boot back into gateway, plug in the power for your router, check for GW3D firmware and update it without going out of settings.

As an extra extra protection, you can also enable parental controls on your real NAND and have it off on your emunand.

I hope this helps.

 

[Purple_Shyguy]

isnt disconnecting from a firmware update dangerous?

 

[Jayro]

isnt disconnecting from a firmware update dangerous?

No, because it's just the potential download of the firmware that gets interrupted, not the installation of the firmware. Breaking a download isn't harmful to the system in the slightest.

 

[Arras]

isnt disconnecting from a firmware update dangerous?

As long as you shut down the router and not the 3DS itself it's perfectly safe, because it tries to download the whole thing before installing it.

 

[sudeki300]

Safest way I found was after you have set up the emuNAND and set up a wireless connection, turn the 3DS off and then boot into gateway mode and go straight into settings and up date from there. That way there is no chance of the 3DS resetting / rebooting itself back into the system NAND....................sudeki300

 

[Keoje]

Safest way I found was after you have set up the emuNAND and set up a wireless connection, turn the 3DS off and then boot into gateway mode and go straight into settings and up date from there. That way there is no chance of the 3DS resetting / rebooting itself back into the system NAND....................sudeki300

If I do this and obviously SystemNAND won't have any wireless connection set up. It's pretty infallible right? Then I am free to do System Update and access the E-Shop in Gateway mode? (Or is it Classic????)

 

[sudeki300]

When you set up the wireless connection in emuNAND mode it will reset / reboot the console back into the system NAND, that's why people who have gone from internet settings straight into the other settings to do the system update have updated their system NAND to the latest firmware and lost 4.5 firmware. Doesn't matter in which NAND you set up the wireless connection in they will still be there in either system NAND or emuNAND, what I did was make a folder in the emuNAND home menu. That way you can easily tell which one your in before turning on the wireless connection.................sudeki300

 

[temp1312]

When you right after click the system update, it will always give you a "agree or not" thing, it that a so called TOS? is that safe?

I mean this: this agreement always shows up.

-Accept the agreement and when you see the download dialog with the blue progress bar, disconnect the power to your router.

 

[Subtle Demise]

When you set up the wireless connection in emuNAND mode it will reset / reboot the console back into the system NAND, that's why people who have gone from internet settings straight into the other settings to do the system update have updated their system NAND to the latest firmware and lost 4.5 firmware. Doesn't matter in which NAND you set up the wireless connection in they will still be there in either system NAND or emuNAND, what I did was make a folder in the emuNAND home menu. That way you can easily tell which one your in before turning on the wireless connection.................sudeki300

Wait...so internet settings are persistent between emunand AND sysnand? How is that possible?

 

[dagro]

Wait...so internet settings are persistent between emunand AND sysnand? How is that possible?

Try setup net on emunand and reboot and go into realnand and you will see the settings you added. It doesn't work the other way round (add in realnand and found in emunand). This is where it gets troublesome because you will still SEE GW3D as the firmware version right after adding internet connection however the system just booted you out into realnand to add the connection so if you choose to update right away then you are screwed.
Its best to always run the task you came to do in settings and reboot after every task. This means don't go around clicking randomly in setting as you may see GW3D for firmware but it may be sharing data with realnand.

 

[LolGuyX]

I tested this extra step and it doesn't work.
You have to accept the download each time you press ''system update'' in the options.

 

[ginryu]

Wait...so internet settings are persistent between emunand AND sysnand? How is that possible?

Not really, when you set up a connection in emuNAND will show to on sysNAND but you can delete it from your sysNAND and it will still be on emuNAND.

 

[mznova]

I tested this extra step and it doesn't work.
You have to accept the download each time you press ''system update'' in the options.

Yeah, there should only be one "accept" that you have to press the final time you do it. The method ensures that if there are more than one the first time you do it, you are still safe because you blocked the update by powering off the router. The second time you do it, you should have already accepted all the agreements so there is guaranteed to be only one left (and so you can be sure you won't get kicked back to real nand).

 

[Schizoanalysis]

Excellent.

Thank you.

I just updated my emuNAND successfully!


What I did (for successful update):

1) Follow Gateway steps to set up emuNAND
2) Change icons on sysNAND (make smaller), and leave emuNAND icons big
3) After setting up Wifi settngs in emuNAND, boot into sysNAND and delete Wifi setting in sysNAND, leaving Wifi settings only in emuNAND
4) Set up parental controls in sysNAND (no parental controls in emuNAND)
5) Boot into emuNAND, go to SETTINGS/update, but turn off router during first update
6) FINALLY, boot into emuNAND, check icons are correct size for emNAND, click SETTINGS, check GW3DS in front of number, go straight to OTHER SETTINGS/update, cross fingers and update
7) profit!

 

[Stormwolf64]

So, you say we should shut of the router when starting to download the update, but you haven't mentioned why. We are booted back to sysnand after doing this, so what are we looking for? And can't you simply slide of the wireless on your 3ds instead of shutting of your router?

 

[Foxi4]

Or the users could follow Gateway Team's instructions word-by-word... That's also an option.

 

[my2k2zx2]

I just put an S folder on my sys nand and an E folder on my emu nand, placed in the lower right.

 

[zb123]

I just put an S folder on my sys nand and an E folder on my emu nand, placed in the lower right.

What I did was put the health and safety icon (a big exclamation mark) on my says and because it sticks out.

 

[telumetan]

Is it even necessary to do this extra step...? Any basis? Many people updated fine with just following instruction, I'm sure they had to go through the agreement screen as well yet they didn't update their sysNAND, just their emuNAND.
And do we have to do this at every update or only on the initial update?