Hardware Add +1 to the 3DS death count shall we?

[Devin]

Update: The GW3DS team have replied saying that they are covering shipping my bricked 3DS XL system to them in order to see why it bricked. I've agree'd to do so but in the mean while this topic has gone as far as it can in terms of actual discussion and has resorted to slander as well as spam. So I'm closing the topic until I get a reply from the GW3DS team telling me the cause of my 3DS bricking. Which their initial consensus is that my 3DS XL was bricked due to potentially having a developer GW3DS unit. So until then thread = locked. If you have some input there are a few other brick threads or if you have a question for me directly click the PM button.

Thanks.


Original Post:

Spoiler

Sup. So I decided since my internet was out and it still is. (I'm leeching off a friend's internet on one bar but it'll suffice for my needs.) That I would play a 3DS game using my GW3DS on my 4.5 3DS XL system. Having known about the bricks I was very cautious. I used the R4 included with the GW3DS kit to install the DS exploit and used the download I had downloaded previously from the Gateway website for firmware 2.0b. I've already MD5 checked them to be legitimate and not edited in any way possible. So going onward I booted into GW3DS mode or tried to I should say. Each time I tried it would give me a black screen and on the third try I decided to give up on playing. Turning on the system once more resulted in a blue screen.

I'm no novice when it comes to 3DS flashcart and I'm in no way shape or form trying to fuel hatred. I just wanted to let other people know that my personal 3DS XL system bricked. Even though I was extremely cautious so that it wouldn't. I plan on emailing the GW3DS team to attempt to help them determine the cause of my brick and also to see if they'll replace my 3DS XL..

It's a shame really. I mean I don't even really play my 3DS XL that often to warrant me being pissed. I'm mostly eh about it since I do own a legit 3DS system on 7.0 for my needs but I would like to see how the GW3DS team handles this. Questions?

 

[gamefan5]

Ok, if a legit reviewer got a legit brick, a legit reviewer of GW, then I am inclined to believe it at 100%.

 

[Warrior522]

Good lord, even you, Devin? This IS worse than I had figured...

 

[Armadillo]

Confirmed. Devin=Chinese Mafia .

Serious note . I've switched back over to my sd with emu 6.3 and b1 for now. Until this mess is sorted out.

 

[the_randomizer]

Damn, that sucks dude. With this much backlash, they are either going to have to rectify it or, well, continue to refuse to support customers

 

[Arras]

I only have one question: IIRC, your 3DS is hardware modded. Does restoring the NAND work? Probably not, but it's the best way to check whether the brick is gateway-related.

 

[WiiUBricker]

Gateway is worse than Sony the Mafia.

 

[Devin]

My 3DS XL had the NAND dumping wires and everything taken out once the emuNAND feature was released.

 

[Arras]

My 3DS XL had the NAND dumping wires and everything taken out once the emuNAND feature was released.

Ah, too bad. Oh well, it's probably safe to assume it's brick code-related anyway.

 

[aireca]

Details man, for example which emunand firmware had your SD

 

[Devin]

I had no emuNAND firmware on my SD card. I was previously using my 3DS' 32GB SD card in my Wii. I formatted the SD card and then put the GW3DS launcher.dat file onto the SD card. Everything else I did to make sure it wouldn't brick is in my first post. I've emailed the GW3DS team explaining my situation and will post their reply once I get it.

 

[Ryukouki]

Well that's a damn shame.

 

[R4iFanboi]

They made their money. They don't care about us.

 

[profi200]

I have given all informations i have and can give. If that is not enough, then i really don't feel sorry for the defenders.

 

[PolloDiablo]

Time to update this one?



I'm sorry for your loss, may your 3DS rest in Valhalla!

 

[pwsincd]

in a twisted way , im kinda glad someone round here that has a track record and legitimacy has experienced this , as all the supposed reports seen to come from relative noobs to this site and others , and that did lend some weight to the clone card fake account speculation , i was unsure either way. But after reading Devins experience of which im sorry to hear fella , im now convinced they had either a intended this , or fukked up in some way,either way Gateway need to address this properly and stop all the cloak and danger shite.

 

[Ryukouki]

While it's completely regrettable, this actually could be quite interesting. We have here an established reviewer on site having issues, playing a "legitimate" Gateway only console, and having encountered this same issue. I'm actually very curious to see how they respond, going that he's a GBAtemp reviewer, given that his repair process may be different going by the fact that he has no vendor to purchase from to contact so that he can initiate the RMA.

 

[jqrn]

Sup. So I decided since my internet was out and it still is. (I'm leeching off a friend's internet on one bar but it'll suffice for my needs.) That I would play a 3DS game using my GW3DS on my 4.5 3DS XL system. Having known about the bricks I was very cautious. I used the R4 included with the GW3DS kit to install the DS exploit and used the download I had downloaded previously from the Gateway website for firmware 2.0b. I've already MD5 checked them to be legitimate and not edited in any way possible. So going onward I booted into GW3DS mode or tried to I should say. Each time I tried it would give me a black screen and on the third try I decided to give up on playing. Turning on the system once more resulted in a blue screen.

I'm no novice when it comes to 3DS flashcart and I'm in no way shape or form trying to fuel hatred. I just wanted to let other people know that my personal 3DS XL system bricked. Even though I was extremely cautious so that it wouldn't. I plan on emailing the GW3DS team to attempt to help them determine the cause of my brick and also to see if they'll replace my 3DS XL..

It's a shame really. I mean I don't even really play my 3DS XL that often to warrant me being pissed. I'm mostly eh about it since I do own a legit 3DS system on 7.0 for my needs but I would like to see how the GW3DS team handles this. Questions?

sry if I can't see i from the text. But what firmware are/were you on? was it 2.01b or 2.02b?

im on 2.01b and I am starting to get really nervous now

 

[kingsora831]

Perhaps your SD card was corrupted which caused the launcher.dat to not run correctly and in turn cause the brick code to go off and then the blue screen.
I know i used a 32gb SD in my wii as well and after sometime the SD card had gotten corrupted, and even formatting didnt help, i ended up just using a spare 4GB i had for my wii.
But perhaps the same happened to your SD card. Did you have any trouble running homebrew on your wii w/ the card? (i did, which resulted in me formatting and then just switching SD cards)

Either way, this just shows that 2.0b2 is not safe regardless what GW says, and if they dont remove it in Ver 2.0 (if it ever comes) it would be a waste of an update because many wont be willing to risk their 3ds.
Goodluck on getting your 3ds Fixed tho, hopefully being a review will help cause GW to repair yours more quickly & for FREE.

 

[Tomy Sakazaki]

Perhaps your SD card was corrupted which caused the launcher.dat to not run correctly and in turn cause the brick code to go off and then the blue screen.
I know i used a 32gb SD in my wii as well and after sometime the SD card had gotten corrupted, and even formatting didnt help, i ended up just using a spare 4GB i had for my wii.
But perhaps the same happened to your SD card. Did you have any trouble running homebrew on your wii w/ the card? (i did, which resulted in me formatting and then just switching SD cards)

Either way, this just shows that 2.0b2 is not safe regardless what GW says, and if they dont remove it in Ver 2.0 (if it ever comes) it would be a waste of an update because many wont be willing to risk their 3ds.
Goodluck on getting your 3ds Fixed tho, hopefully being a review will help cause GW to repair yours more quickly & for FREE.

Even with the first case that happened with a alleged legit gateway user (Apolooooo, idk how to write, sorry) it seems that the file or the SD doesn't need to be corrupted at all to make the 2.0b2 brick a 3DS, all it needs is to get into a wrong instruction of the launcher.dat to make the console brick, a.k.a. program bug.
As a fellow Gateway user (since 1.2) I recommend that GW users downgrade their launchers to 2.0b1 or 1.2 and if possible stop using emunand functions, until gateway stop putting bricker codes on their files, or even better, some one launches a patched version with all instances of it removed.