Hacking GATEWAY 3DS IS PREPARING A BIG UPDATE IN APRIL!!

[Kioku]

Well, it's good they're still supporting the product.

 

[Aurora Wright]

Inb4 soundhax + fasthax + safehax copy-paste is the "major update"

 

[lafleche]

Mhhhhhh...brickway????
Only a few known cases and even those were not very well documented....

However.... The countless posts of people bricking their 3ds with cfw are okay because these bricks are for free????? Don't make me laugh!

 

[godreborn]

they need a9lh support for higher versions than version 1 like sd card less.

 

[proflayton123]

Personally, it amuses me how people shitpost over something they don't own, then again it's just as bad seeing Luma fan boys..

 

[evandixon]

Funny how everyone joking about the bricks forget about the clones that made the dormant brick code active then delivered it to their customers.

And don't go on about how GW users were bricked. A9LH has bricked far more people (even if you exclude the user-caused bricks), and it doesn't get nearly as much hate as GW.

 

[Kioku]

How many people do you think have owned one of their carts?

 

[WiiUBricker]

So when are they going to release the "surprise feature" they promised who knows how many moons ago?

 

[MadMageKefka]

So when are they going to release the "surprise feature" they promised who knows how many moons ago?

...in April. Lol.

 

[Kioku]

Funny how everyone joking about the bricks forget about the clones that made the dormant brick code active then delivered it to their customers.

And don't go on about how GW users were bricked. A9LH has bricked far more people (even if you exclude the user-caused bricks), and it doesn't get nearly as much hate as GW.

At least the A9LH devs owned up to the bricks. There was also a huge disclaimer of "use at your own risk". Gateway offered an exchange/refund program... Which died soon after.

Not to mention this was a long ass time ago. They haven't bricked anyone in a while.

 

[CrimsonMaple]

My question is are they gonna actually release it in April? #SOON™

 

[evandixon]

My question is are they gonna actually release it in April? #SOON™

I'll believe it when I see it. They haven't even officially "released" A9LH support. It's still a private beta that's clearly marked as not being for anyone without a hard mod.

 

[proflayton123]

I'll believe it when I see it. They haven't even officially "released" A9LH support. It's still a private beta that's clearly marked as not being for anyone without a hard mod.

Yet people still used it

 

[Deleted User]

This is great news. Once again Gateway shows why they have been and always will be the best flashcart on the market.

That's not me being a fanboy, this is just an objective observation. My privileged ass has been fortune enough to sit through the 3DS's sycle since the beginning of the 3DS and what a glorious ride it has been for Gateway. Not a single flashcart company has been this great for the 3DS community. If history would repeat itself all of us would choose Gateway and you know it.

 

[linuxares]

Funny how everyone joking about the bricks forget about the clones that made the dormant brick code active then delivered it to their customers.

And don't go on about how GW users were bricked. A9LH has bricked far more people (even if you exclude the user-caused bricks), and it doesn't get nearly as much hate as GW.

Because A9HL you KNOW you can brick. What GW did was to implement a way to destroy your hardware because they were crying kids that their pirate device get pirated.

 

[Zaphod77]

There are 4 ways to handle clones

1) don't.
2) detect and warn.
3) brick the clone itself
4) brick the console.

R4 team has tried number 2.

TTDS team tried number 3. then the clone makers cloned the killer code and made it not kill theirs and kill the originals. they even posted a fake detection page that was the opposite of original. (i'm talking about CN-TTDS, specifically. there may be other clone makers that did that too.)

I consider number 4 unforgivable, since people may not always know they got a clone. and the same thing that happened with ttds could happen to teams who use method 4 as well.

Were i making flashcarts, I would go for number 2. 3 and 4 victimize people who think they are getting the real deal. I would pop p a 1 tie message stating "This flashcart is an unauthorized clone. It may have compatibility issues that the genuine product does not. If you paid more than 5 bucks for this, you got ripped off." (chuckle)

 

[morvoran]

There are 4 ways to handle clones

I consider number 4 unforgivable, since people may not always know they got a clone. and the same thing that happened with ttds could happen to teams who use method 4 as well.

I also agree that this method is kinda shady, but the same can be said about buying flash carts to pirate video games. You shouldn't go to a secluded alley to buy stolen goods and then get upset when the guy robs you. If you are going to do shady/illegal things, you should never go in blind. In other words, people trying to save a couple of bucks buying clones and then get bricked deserve it if they don't research what they are buying first.

 

[Zaphod77]

Even with research, it's not always that easy to tell. when we mix in clones that have firmware the bricks originals instead... even good sellers get taken in sometimes. it's so bad that to be an official ttds reseller you had to offer to replace bricked cards.

Using the famous theft analogy, number 2 is going into your house and placing a note on the item, number 3 is going into the house and destroying only the item and also leaving a note, and number 4 is destroying the persons entire house for containing the stolen item the person may not even be aware was stolen.

You see why i do not like number 4. 3, while shady, is still forgivable, because it's only destroying the clone. Bricking the other person's legitimate property is NOT COOL.

I suspect that Gateway did number 4 because they couldn't actually do number 3. But it's still evil.

 

[Armadillo]

Even with research, it's not always that easy to tell. when we mix in clones that have firmware the bricks originals instead... even good sellers get taken in sometimes. it's so bad that to be an official ttds reseller you had to offer to replace bricked cards.

Using the famous theft analogy, number 2 is going into your house and placing a note on the item, number 3 is going into the house and destroying only the item and also leaving a note, and number 4 is destroying the persons entire house for containing the stolen item the person may not even be aware was stolen.

You see why i do not like number 4. 3, while shady, is still forgivable, because it's only destroying the clone. Bricking the other person's legitimate property is NOT COOL.

I suspect that Gateway did number 4 because they couldn't actually do number 3. But it's still evil.

Gateway went with number 4 as they tried other methods first. Not like they went scorched earth straight away.

They went with save corruption to start with. The clones would randomly delete your saves. Clones carried on, kept releasing "renamed" firmwares claiming to fix the "bug", while the users of the clones paraded around the forums shitting up GW threads and claiming they don't care if they have to backup the saves every now and then because they paid half price.

4, while extreme, ended it all. GW is the last flashcart standing. A free cfw was always going to prove a more popular regardless of Gateways actions, but 4 ended the clones.

Also for what it's worth, people don't seem to have a problem with 4 when it's Nintendo doing it (cue list of reasons why intentionally bricking region changed korean wiis is somehow different and justifiable).

 

[Zaphod77]

I can't use it regardless now. only thing they have to recommend themselves is their cheat finder, which IS actually nice.

as someone who isn't really inclined to cheat, they currently have nothing at all to offer me.