I can tell disturbing facts about that :Is it not strange, all bricks happened at the same day?
I'm 100% sure they included time related bricking code. And as we know, their hardware diagnostics are not very reliable, the clone detection maybe fails too --> brick, even with the original GW
- 04.01.14 : x2 3DS XL consoles sold to a customer there is a week with R4iGold v3.2 + emuNAND 7.1 (installed by myself)
-> One of the 2 consoles bricks Saturday, 11
The customer comes back with the 2 consoles yesterday (13.01.14) and I exchange the bricked console by new one (v3.2 + emuNAND 7.1) and make new installation of the other (v3.2 + emuNAND 7.1 again).
-> After 1 power on and test of "Bravely Default" game, the customer turn of each console and returns home. Once home, when he tries again, the 2 consoles crash just after launching "R4iGold mode". When he restarts them BSOD appears.
- 06.01.14 : x1 3DS XL console sold to a customer (R4iGold v3.2 + emuNAND 7.1 make by me), sent by post, he received it Thuedsay 9 and played only "Luigi's Manson 2" game with it until saturday 11.
-> I contact him by phone today to alert about the RSOD issue and when he tests it in the same time (just switch on) RSOD appears !
I think from saturday, the bricking code started to operate and GW team is under this.
Like the time of PS3 dongle, TrueBlue team has placed malicious code that affects randomly JB-King dongle user by crashing the console HDD.
Ways are the same and I also think they are the same teams (Gateway = TrueBlue).