Short Version:Could someone please help me with a small explanation of the bricking scandal? So much information is scattered across so many different threads that it's almost impossible to follow.
The GW launcher.dat 2.0b2 seems to contain code that can f-up the 3DS memory chip, as of yet without a known way to repair it, although it seems that there will be no software only fix for sure.
It is reported to trigger especially when using modified versions of said launcher (like the cloners (r4i, 3dslink, orange) or the region free patch), I'm aware of fifty-ish reports so far strewn across different boards of bricked 3DS's from users who claim to have used a modified launcher.
GW released a statement that it is save to use as long as one doesn't modify it, but there have been reports (one here, one in the official support forum, one in a spanish forum) from users who claim to have run into bricks using the official version.
Current debate/speculation topics (besides the usual bitching and moaning) are:
- if the code is there on purpose (cloning deterrent) or if it's a unintended leftover (GW mentioned they tried a way to prevent accidental updates but had to pull it because it caused bricks)
- if GW is justified in bricking end user consoles on purpose
- how likely it is to brick ones 3DS (is it safe to run modified? is it safe to run unmodified?)
The only real consensus is that GW 2.0b1/ r4i 3.3b are safe, so you might want to switch to one of them, although some (me included) stay with 2.0b2 (can't help it, am a thrill seeker)
You might want to read some of the threads none the less, some are quite entertaining and popcorn worthy.