To avoid accidental update real nand

Discussion in '3DS - Flashcards & Custom Firmwares' started by Enigma Hall, Dec 4, 2013.

  1. Enigma Hall
    OP

    Enigma Hall GBAtemp Advanced Fan

    Member
    677
    204
    Feb 6, 2013
    Brazil
    My gateway is on the way and i´m reading about this problem.

    My idea is to create a different user profile to emunand, it could make more safe to identify what nand you are in. You can look the profile name to make sure if you are in the emunand before update.

    But the question is. My idea work?
     
  2. how_do_i_do_that

    how_do_i_do_that Blue Wizard is about to die.

    Member
    4,951
    270
    May 16, 2008
    Antarctica
    You have insufficient posts to view user location.
    Murphy's Law: if it can go wrong, it will happen.

    Best way to safeguard against it is to add the hardware mod for dumping and restoring the NAND. This will let you make this mistake without risk on your part by allowing you to restore the 4.X firmware to a 3DS XL that was mistakenly updated.

    3DS XL mod topic: http://gbatemp.net/threads/nand-flash-dump-3ds-xl.350668/
    A more recent and condensed version of the same topic: http://gbatemp.net/threads/backup-and-restore-gateway-2-0.358582/

    You make a NAND dump of your 4.X firmware (via the hardware method, to make sure it is soldered correctly and dump is correct size and is the same after several dumps), then save it somewhere safe.

    ---

    As for you idea it is only prudence on any user's ability to tell the difference between which mode they are in. It still doesn't remove the "permanent fail" situation.
     
  3. mickcris

    mickcris Advanced Member

    Newcomer
    54
    13
    Nov 15, 2006
    United States
    I made a folder in each and labeled one realnand and one emunand and put it on the 1st page of icons next to the cart icon and settings icon.
     
  4. Ryft

    Ryft GBAtemp Advanced Fan

    Member
    546
    188
    Nov 21, 2013
    United States
    Illinois
    I have a theory that the parental controls are seperate on SysNAND and EmuNAND... if so, you could just set the SysNAND and EmuNAND to block everything BUT have a seperate PIN for each (I would write them down). When you try to update, it should ask you to insert the pin. If you put the wrong PIN in, it just won't let you download the update. I can't test this myself since I am not making an EmuNAND until a more stable release comes out. If someone could test if the parental controls are seperate or not, that would be helpful.

    Of course this is totally useless if there is some rare glitch that causes it to update the SysNAND after downloading the update anyway...:P
     
  5. KidIce

    KidIce Smart Ass

    Member
    952
    261
    Dec 22, 2005
    United States
    No, that won't work. Doing almost anything in the System Menu that isn't updating your 3DS (or more to the point, your emuNAND) ejects you from GW mode. If you alter your user profile while in GW mode when you are done you will find that your are back on your old/"real" firmware and no longer in GW mode or using emuNAND. Just follow their instructions: Make sure "GW3D" is replacing the "Ver.", only update from the System Menu. If both conditions are true, you need no more safe guard than that.