Moved my post from the second page to here, so more people can see it.
-----------------------------------------------------------------------------------------------------------------
Just read though the entire german thread (translated) and this is what I got out of it.
- Gateway 3ds Clones will have their system NAND corrupted and the system NAND reader corrupted - no easy fix, if any at all.
- Gateway 3ds users with SD corruption issues can get this brick.
EDIT 2: Apparently, GW has a sanity check to check for corruption. You should be safe with an unmodified GW launcher.
The Region-Free patch for the Gateway 2.0b2 firmware does not have this bricking issue. EDIT: Apparently, it does.
Recommended Actions:
- Don't use the Region-Free patch - It will brick your system
- Don't use R4i 3ds Gold Deluxe or 3DS Link or Orange 3DS on any firmware equivilent to 2.0b2!
- If you are using Gateway, make sure not to download your launcher file from an external source!
If you are using a Gateway, and afraid you have a bad launcher.dat, you can perform a checksum.
BTW, i just did a checksum of my launcher.dat and its.
SHA: 3508a54dd3b1ff903fbf18ecf97b075205b67d0c
MD5: 6361c5d4935af6d888ffc0646548f5dd
As for actually performing the checksum...
http://gbatemp.net/threads/brick-protect-3ds-for-gw2-02b-users.360580/#post-4884288
Foxi4 was so kind as to write a program that will do it for you. Simply put your launcher.dat and his program into your NDS flash cartridge, and run it.
Note that this is almost arbitrary at this point. It is all but confirmed that GW users are completely safe... provided they are using unmodified files.
The rest of this thread is basically clarifying that NAND restore
WILL NOT FIX THE BRICK and discussing the politics of the situation, with the occasional Noob telling everyone it is no big deal, and safe for GW users.
EDIT 2: As stated earlier, apparently there is a sanity check in place that will not run code from a corrupted file.
Source:
https://twitter.com/Mathieulh
-----------------------------------------------------------------------------------------------------------------
Personally, I think that gateway had better remove this code, otherwise they are going to be scaring off all of their customers. It does rather throw a wrench into the clones of the Gateway though, as now they cannot copy Gateway's work. We just are unlucky enough to be caught in the middle of all this.
Here's to hoping that the Gateway devs will remove this malicious code in the 2.0 Release. If they don't we are going to start having the brilliant people in the community patch all the launchers, which is no fun.