Whats with everyone all of a sudden having bricks? seriously is it a firmware update or is this the cool hip thing to do with flash carts?
Whats with everyone all of a sudden having bricks? seriously is it a firmware update or is this the cool hip thing to do with flash carts?
Well, Playtronics is one of the official GW resellers here in Brazil (http://www.gateway-3ds.com/resellers.html), so it's very unlikely that OP got a cloned flashcard.
Feel sorry about your loss, bro. Try to contact Playtronics again to see if GW informed them about the RMA procedure.
Sim, sempre comprei na playtronics é uma loja confiável então sei que eles farão o possível para resolver.
I asked about 7 questions on the systems getting bricked I guess no one knows the answers.
http://gbatemp.net/threads/3ds-just-bricked-with-a-legit-gw.360799/ #297 & 301
when was the first 3ds reported brick that was put on gbatemp? (date)
what sysnand and emunand firmware was used when the brick happened?
was the time and date set correctly on the 3ds system when the brick occurred?
when the exploit executed did they update the blue card or just update the launcher.dat file?
was wifi on at the time of the bricking?
was the system in sleep mode or turned on played then turned off then turned back on bricked?
ssame goes for the other 3ds that got bricked just comparing to ee if anything stands out.
(Let's keep the conversation in english, ok? This is an english speaking forum, so we need to respect it. )
I wish you good luck. I'll ask you to keep this thread updated if you receive an answer from them.
^ just use 2.0b1.
Guys just wondering, could the error be related in realNand date being different from the emuNand date? So when 3ds boots to emunad it doesn't match (something in the code) and it bricks?
I've read all of these hundreads of threads a we still don't have a reason or how the brick is caused.
btw, I'm on 2.0b1 just to be safe, and I wont turn it off until we have more info