[Question] emuNAND on 2.x

Discussion in '3DS - Flashcards & Custom Firmwares' started by Robz8, Mar 3, 2016.

  1. Robz8
    OP

    Robz8 Coolest of TWL

    Member
    6,694
    2,830
    Oct 1, 2010
    United States
    Is it possible to get 2.x emuNAND working, maybe in the future? It would be easier to dump the OTP, without having to do it in sysNAND.
    Why doesn't it work, currently?
     
    Last edited by Robz8, Mar 3, 2016
  2. Lord Socky

    Lord Socky Newbie

    Newcomer
    9
    15
    Oct 1, 2015
    United States
    Making a stab in the dark here because I don't know for certain, but I feel this is a safe assumption to make. The reason we have to downgrade to 2.X is because prior to 3.0, the OTP wasn't protected. After 3.0, it's protected very quickly during boot. With your current 9.2 system, by the time your *hax loads and starts the transition to emuNAND, it's already been protected at boot time and loading emuNAND doesn't reboot the system. A 2.X emuNAND still can't access the OTP, because it was already protected by the 9.2 sysNAND.
     
    Omegadrien likes this.
  3. dankzegriefer

    dankzegriefer GBAtemp Advanced Fan

    Member
    829
    437
    Aug 19, 2015
    United States
    OTP IS LOCKED BY SYSNAND
    YOU NEED A SYSNAND THAT DOESN'T LOCK IT.
     
  4. SirByte

    SirByte GBAtemp Fan

    Member
    494
    191
    Dec 30, 2012
    Canada
    No need to yell.

    But it is correct, when your sysnand (3.0.0 or higher) starts up your 3DS, it locks access to the OTP area, so lonnng before you can even start EmuNAND.

    Why it would still be great to have 2.1 emunand is that it allows you to boot the emunand, see if it's alright, shut down and dump your emunand, rename it and flash it to sysnand, then restart again to dump OTP. Right now after downgrading your EmuNAND to 2.1.0 you still have to take the Leap of Faith to flash it to sysnand untested.