Dodgy yes.
Just not as dodgy as what r4i and the other Gateway clones do.
How do you figure that? Gateway targeted and intentionally bricked consumer devices. That's a lot dodgier than cloning somebody's product.
Dodgy yes.
Just not as dodgy as what r4i and the other Gateway clones do.
How do you figure that? Gateway targeted and intentionally bricked consumer devices. That's a lot dodgier than cloning somebody's product.
Gateway is impersonating a guard for the 3DS and did the research to get the keys/codes to gain access. This situation is just clones trying to steal Gateway's business of letting unauthorized people in by stealing a copy of their latest keys/codes. It isn't Gateway's fault that their competition ripped them off and sold the booby trapped keys/codes without proper research on how they work.
Hm, your aren't exactly the longest member of this community either... Gateway crew member? (But only for marketing/social influence, it is obvious your technical background is lacking...)
And roughly half of your awesome 200+ postings consist of "Gateway is awesome - I knew it all along - you dirty clone card supporters got what you deserve - Gateway's security checks to not brick a console with untouched launcher.dat are infallible"
So let's summarize: No 3DS game released until today will brick your console! Stay with the original authors and developers!
If you like my post buy yourself a game!
EDIT: For everybody requesting the "bricking code" instead the pseudo code (from neimod?/yellows8?/whatever)
.....
.....
Hm okay maybe this is the 3rd image a google search for "asm code" gives, but for most of the people asking for code this should suffice...
It is still the clones card firmwares that brick devices, and so it is their responsibility. Gateway does not have to make her software easily copyable to make sure they work on all kind of clone cards.
If the copycats are not able to crack GWs bricking routine, it is completely their fault to release this stuff.
How do you figure that? Gateway targeted and intentionally bricked consumer devices. That's a lot dodgier than cloning somebody's product.
But Gateway have shown a blatant disregard for consumers by coding an intentional device brick into their launcher in the first place.
I agree with you that their's a level of responsibility that lies with the clone companies. But Gateway have shown a blatant disregard for consumers by coding an intentional device brick into their launcher in the first place. If they wanted to protect their products, they should have looked for another way.
Although it could be that the MT-Card uses a very old internal beta version.In a rather karmic turn of events, the only clone that didn't break was MT-Card, which was based upon an older version of the GW firmware with new additions being made by the MT-Card team itself instead of copying straight from GW.
So running unauthorized software is okay, but running unauthorized modifications of unauthorized software is a no? lol
Although it could be that the MT-Card uses a very old internal beta version.
Although it could be that the MT-Card uses a very old internal beta version.
The launcher has Firmware spoofing (for SDK 5.X games), Region Unlock, a GUI and Multi ROM. Nothing more and nothing less. Firmware Spoofing and Region Unlock have been included into the 1.2 launcher, GUI and Multi ROM not.That's likely. The brick code was only introduced in 2.0b2. The fact that MT-Card doesn't even have EmuNAND, region free or any of the GW patches suggest that the GW firmware must originally predate 1.2.
That is how you see it.
Gateway didn't brick any devices.
I think the inept r4i team failed to protect their customers.
I guess when your product is made by people who know jack squat, you are at risk.
Maybe the r4i team can learn how to make their own product, until then the only safe card is a Gateway.
Jesus christ these images. Make them smaller, please.
Hey, don't give Microsoft any ideas!So you'd be perfectly fine with Microsoft adding a killswitch to every single copy of Windows (legit/illlegal)? Once a certain event (timeframe, open a certain window/program, etc) happens, the program will fry your computer since it wasn't an OEM flash drive (flashcart) that you used to replace the HDD (game cart). This is basically what the situation is. Regardless of opinion.
Methinks this is more likely to happen now than it was before.Until someone creates an open source launcher, it doesn't matter what Gateway did or did not do. -snip-
EDIT: For everybody requesting the "bricking code" instead the pseudo code (from neimod?/yellows8?/whatever)
.....
.....
Hm okay maybe this is the 3rd image a google search for "asm code" gives, but for most of the people asking for code this should suffice...
that is completely true.If they wanted to just fuck up the cloner's 3DSes, they would have made it brick 100% of the time instead of randomly. I'm assuming they did this to make it seem like the clone cards are unreliable, not to mess with the cloner's 3DSes. Testing wouldn't help since it's random. It could just not appear in testing.
they didn't expect it, that is why they put in that code hahahaYou can't expect to publicly release something like this without having at least a few copycats arise.
I can understand Gateway being upset at being plagiarized and undersold, but still, responding with destructive AP?
Yeesh.