Hacking Is 2.0b2 safe without emuNAND?

[COLD_SNAKE]

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.

 

[Warft]

NO.
The only launcher safe is GW 2.0b1 or clones 3.0.

 

[Arras]

NO.
The only launcher safe is GW 2.0b1 or clones 3.0.

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.

 

[profi200]

Even without "emuNAND" it is not save.

 

[Deleted User]

To be on the safe side, use 2.0b1 or 1.2 until GW releases a new fw

 

[Deleted User]

i deleted the "launcher.dat" file from the sd card a moment ago.

now i must be safe. right?

 

[kirillov]

Downgrade to b1 until new releases

 

[COLD_SNAKE]

I already downgraded when it was confirmed there was a bricking code.

 

[Punkrox]

Even without "emuNAND" it is not save.

Yeah it occurs on launch so I doubt emuNAND is the cause

 

[COLD_SNAKE]

Yeah it occurs on launch so I doubt emuNAND is the cause

I thought the brick modifies the eMMc when you try to return to sysNAND, hence why it bricks when you exit system settings.