Hacking WTF?????? NAND Updating Gone Wrong!

[kyogre123]

what are these new names you speak of... what happened to emuNAND and ermm... NAND ??

Ignore that. He's using that name because of mere personal preference, but he's still referring to the same thing.

 

[IronClouds]

what are these new names you speak of... what happened to emuNAND and ermm... NAND ??

redNAND is the more technically accurate term since the detection of the NAND is being redirected to the one that's on the SD card rather than the one on-board. And I guess phyNAND is easier than typing "real NAND" or anything like that. Probably not easier than just calling it a NAND, but then people would get confused at that, I'm sure (do you mean the emuNAND or the real NAND? etc. etc.).

 

[kyogre123]

redNAND is the more technically accurate term since the detection of the NAND is being redirected to the one that's on the SD card rather than the one on-board. And I guess phyNAND is easier than typing "real NAND" or anything like that. Probably not easier than just calling it a NAND, but then people would get confused at that, I'm sure (do you mean the emuNAND or the real NAND? etc. etc.).

Nope, it's not accurate; the emulated NAND doesn't behave like the real NAND, so just saying that is the same as the NAND but just stored and booted from another location is a fallacy (from my point of view).

Two relevant differences:
1. Since it can't be loaded after a power cycle, something called keyY is missing. The point of this is that, due to this missing feature, it encrypts save files of newer games differently to the point of making them incompatible with regular updated systems.
2. When you get a new app or game through the eShop, the activation tickets not only are stored on the EmuNAND, but also are written on the actual NAND.

 

[IronClouds]

Nope, it's not accurate; the emulated NAND doesn't behave like the real NAND, so just saying that is the same as the NAND but just stored and booted from another location is a fallacy (from my point of view).

Two relevant differences:
1. Since it can't be loaded after a power cycle, something called keyY is missing. The point of this is that, due to this missing feature, it encrypts save files of newer games differently to the point of making them incompatible with regular updated systems.
2. When you get a new app or game through the eShop, the activation tickets not only are stored on the EmuNAND, but also are written on the actual NAND.

Your argument is that there are two relevant differences between the "emuNAND" and the physical NAND. I'm not disagreeing with you at all. I think you got the wrong idea with my post you quoted, buddy.

 

[Rockstead]

This all scares the crap out of me.

Has the Gateway team improved their instructions based on all this feedback? Or can the ops here make a sticky with better instructions.

Would a non beta release be more likely to have fail safes that would be able to prevent this from happening?

 

[kyogre123]

Your argument is that there are two relevant differences between the "emuNAND" and the physical NAND. I'm not disagreeing with you at all. I think you got the wrong idea with my post you quoted, buddy.

Why? You said it's more accurate but the final behaviour says otherwise. A redirected NAND suggest a redirection and same functionality, but this is not the true case, especially for the second point.

This all scares the crap out of me.

Has the Gateway team improved their instructions based on all this feedback? Or can the ops here make a sticky with better instructions.

Would a non beta release be more likely to have fail safes that would be able to prevent this from happening?

Check the quote I made a couple of posts back

 

[IronClouds]

Why? You said it's more accurate but the final behaviour says otherwise. A redirected NAND suggest a redirection and same functionality, but this is not the true case, especially for the second point.

I don't want to argue semantics with you; it's pointless. Your argument is about a point I never intended to make. So if you misunderstood it, then that's my mistake for wording it in that way. Let's just leave it at that and call it a day.

 

[indask8]

Things I've noticed so far:

- Every time you quit system settings, the 3DS reboot... so you lose gateway mode.

Worse: Wifi settings are shared (I suspect they are saved inside the wifi chip), If you add a connection to your emunand, it will appear also on the original firmware.

My advice is that once you've updated successfully your emunand, disable wifi, better safe than sorry.

 

[kyogre123]

Things I've noticed so far:

- Every time you quit system settings, the 3DS reboot... so you lose gateway mode.

Worse: Wifi settings are shared (I suspect they are saved inside the wifi chip), If you add a connection to your emunand, it will appear also on the original firmware.

My advice is that once you've updated successfully your emunand, disable wifi, better safe than sorry.

My advice would be: Once you have updated the emuNAND; reject any update prompt that could appear; if you wish, check on the internet if a new firmware was released, so you can update following the same careful procedure of before.

 

[Rainbowsixvegas6]

Things I've noticed so far:

- Every time you quit system settings, the 3DS reboot... so you lose gateway mode.

Worse: Wifi settings are shared (I suspect they are saved inside the wifi chip), If you add a connection to your emunand, it will appear also on the original firmware.

My advice is that once you've updated successfully your emunand, disable wifi, better safe than sorry.

I've actually noticed the wifi saving also. What I did when I updated was to delete the wifi settings off of the real nand, and then I noticed that the wifi settings was still stored for the emuNand. I then rebooted and into real Nand and the wifi settings was not stored there.

 

[T3GZdev]

Works fine for me. Backed up nand.y extra eds is on 4.5.0. In gw mode it emus 6.x.x after update but can go back to 4.5.0.

 

[Rockstead]

Why? You said it's more accurate but the final behaviour says otherwise. A redirected NAND suggest a redirection and same functionality, but this is not the true case, especially for the second point.



Check the quote I made a couple of posts back

Not sure which quote you are referring to?

 

[kyogre123]

Not sure which quote you are referring to?

This:

Then I booted in Gateway Mode (not Classic mode), and it showed my Kid Icarus Uprising cart through the Gateway. Entered system settings, and it clearly said GW3D 4.5.0-10U. So I went into Internet settings, added my router, and did a connection test. It made me accept the network agreement, which I did. I then headed over to Other settings, and did a system update. Never left system settings after starting it the first time.

Against this:

Once you have entered into the System Settings application and clearly seeing the "GW3D" version number, enter into WiFi settings and set up a connection.

3) Update your emuNAND partition. Boot into Gateway mode, and enter into the System Settings application.

 

[sudeki300]

ok so can i get some conformation on this as i'm about to update my emuNAND,

once your in the emuNAND and setup the wireless settings, you have to come back out and boot back into gateway mode before updating the emuNAND in the settings menu.......................sudeki300

 

[drfsupercenter]

OK, so... consensus has it that somehow I went back to the real NAND after accepting Nintendo's EULA.

Even though I never actually left system settings.

Well, I wish I would have known that. I was just told not to leave system settings, which I technically didn't. :/

So... who can restore my NAND for me? I'll pay shipping both ways.

 

[Daelan]

100% that it was drfsupercenter exiting the system settings then going and updating, or he setup wireless then went back into settings and updated, both of which would cause his failure.

 

[Rainbowsixvegas6]

100% that it was drfsupercenter exiting the system settings then going and updating, or he setup wireless then went back into settings and updated, both of which would cause his failure.

Yeah I think the mistake he made was after adding the wifi settings, and going straight to update without rebooting back into EmuNand. I noticed that when I added my wifi setting that it also added the same setting to my real nand. It could be that when you add a new wifi connection it reverts back to real nand. I had to delete the wifi settings for my real nand and just left the setting on in emu nand, but disabled wifi.

 

[Daelan]

I can confirm that you have to remove the wifi settings from real nand afterwards to only have them on the emunand. A bit surprising but that's how it is.

 

[drfsupercenter]

I think they should add that to their documentation then.

Once you have entered into the System Settings application and clearly seeing the "GW3D" version number, enter into WiFi settings and set up a connection.

3) Update your emuNAND partition. Boot into Gateway mode, and enter into the System Settings application. CHECK to make sure you see the letters GW3D before the system version located in the bottom right hand corner of the top screen

I took that to mean "once you see GW3D, add a connection, then update". Since I was already *in* Gateway mode... they should make it very clear that setting up a Wi-Fi setting will force you to leave Gateway mode and that you have to shut down your system, and reboot it into Gateway mode once again

Can you really blame me for assuming I was all set when it said GW3D in the bottom right before I went to update it? :/

I'm not mad at Gateway team or anything, just want this to be a warning for anyone else... and I still need someone to flash my 3DS's NAND back for me...

 

[Queno138]

I can confirm that you have to remove the wifi settings from real nand afterwards to only have them on the emunand. A bit surprising but that's how it is.

that occurred to me.
My WiFi settings reappeared in System-Nand/Real-Nand,
so I had to re-delete it in SysNand/RealNand, and confirmed it's only in EmuNand after that.

It's the only way..