Is 2.0b2 safe without emuNAND?

Discussion in '3DS - Flashcards & Custom Firmwares' started by COLD_SNAKE, Jan 19, 2014.

  1. COLD_SNAKE
    OP

    COLD_SNAKE Member

    Newcomer
    40
    4
    Jan 16, 2014
    Swaziland
    Just as the title says is it safe to use 2.0b2 if you're not using emuNAND? From what I've read the brick only occurs when exiting the emuNAND. So I assume it should be safe.
     
  2. Warft

    Warft Say my name!

    Member
    263
    177
    Aug 8, 2013
    United States
    Albuquerque, New Mexico
    NO.
    The only launcher safe is GW 2.0b1 or clones 3.0.
     
  3. Arras

    Arras GBAtemp Guru

    Member
    5,864
    2,679
    Sep 14, 2010
    Netherlands
    Well, and anything before that, including clone 3.3b considering it's the exact same as clone 2.0. Anyway, I'm not really sure if that stuff can happen without emuNAND, but it's probably better to downgrade to be safe.
     
  4. profi200

    profi200 Banned

    Banned
    330
    216
    Sep 3, 2011
    Gambia, The
    Even without "emuNAND" it is not save.
     
  5. json

    json MUSCLEMAN

    Member
    693
    781
    Aug 9, 2013
    Burkina Faso
    To be on the safe side, use 2.0b1 or 1.2 until GW releases a new fw
     
  6. sergey3000

    sergey3000 GBAtemp Fan

    Member
    303
    150
    Sep 14, 2013
    Iceland
    i deleted the "launcher.dat" file from the sd card a moment ago.

    now i must be safe. right?
     
  7. kirillov

    kirillov Advanced Member

    Newcomer
    73
    57
    Dec 10, 2013
    Downgrade to b1 until new releases
     
  8. COLD_SNAKE
    OP

    COLD_SNAKE Member

    Newcomer
    40
    4
    Jan 16, 2014
    Swaziland
    I already downgraded when it was confirmed there was a bricking code.
     
  9. Punkrox

    Punkrox GBAtemp Regular

    Member
    123
    64
    Dec 17, 2002
    Canada
    Yeah it occurs on launch so I doubt emuNAND is the cause
     
    profi200 likes this.
  10. COLD_SNAKE
    OP

    COLD_SNAKE Member

    Newcomer
    40
    4
    Jan 16, 2014
    Swaziland
    I thought the brick modifies the eMMc when you try to return to sysNAND, hence why it bricks when you exit system settings.