Hacking Tx's Official Response to SX Bricking Code

[V-Temp]

Still ignoring the actual question, but at least someone told them that fluffing up numbers is dumb PR for faux reassurance.

At least now I'm fairly certain their original number was bullshit trying to deflect the question.

 

[Armadillo]

Oh yeah, the region changed Korean Wii bricks. I had forgotten about that. Everyone seemed to think that was acceptable for some reason. Even though it was obviously done on purpose since newer IOS checks for the presence of the KOR-specific key.

Caught with pants down, simple as that.

Too busy coming into every GW thread to proclaim "I would never support a company that bricks" that they either forgot or were not around when Nintendo done it. Nothing to do after that except claim "it's different" as if they had any follow through, their 3ds would have to go in the bin.

 

[CaptainLoozer]

My problem with their statement is that they said that they "support" using other payloads. How can they support that if they're telling their customers that if they actually USE their built in feature, they won't support their product anymore? If the intent was to not use any other software, why even put support for other payloads in there? It directly contradicts their own statement.

Edit: Actually now that I've gone back and read it, it seems that they just said they would "allow" it. Good way for them to go back and say you shouldn't have done it.

 

[V-Temp]

My problem with their statement is that they said that they "support" using other payloads. How can they support that if they're telling their customers that if they actually USE their built in feature, they won't support their product anymore? If the intent was to not use any other software, why even put support for other payloads in there?

Marketing.

 

[tnecniv43208]

My problem with their statement is that they said that they "support" using other payloads. How can they support that if they're telling their customers that if they actually USE their built in feature, they won't support their product anymore? If the intent was to not use any other software, why even put support for other payloads in there?

Well that support made me pay, I guess that's it lol, no other reasons that tx wants to support other payloads

 

[CaptainLoozer]

Well that support made me pay, I guess that's it lol, no other reasons that tx wants to support other payloads

I corrected my post. It seems they only said they would allow it. In the event that their software actually does brick your switch, I highly doubt they're going to buy you a new one, even with their "guarantee".

 

[Drakia]

Caught with pants down, simple as that.

Too busy coming into every GW thread to proclaim "I would never support a company that bricks" that they either forgot or were not around when Nintendo done it. Nothing to do after that except claim "it's different" as if they had any follow through, their 3ds would have to go in the bin.

While I was around during the Wii era, I can't say I ever region changed a Korean console... Because why would I?

You're right though, I will say "it's different". First of all, that was 9 years ago, maybe try to find a more recent example? Second, that wasn't trying to brick everyone running homebrew, that was a very specific case that seems rather odd to me.

 

[MasterJ360]

Bricking someone's system is a rather extreme method when there's so many other things they could have done. Honestly the community should be concerned by this because we don't know what's in the source code and a brick code only shows just how little we should trust TX and their code.

If you are a regular user it shouldn't be a concern this brick code didn't surface until someone actually tried to tamper with it on dev level terms givien what info we have I'm not comparing or speculating on other things b/c they aren't TX. The open source community should be concerned b/c they are gonna have to look elsewhere or start from scratch. There's too much fear over 1 victim all its doing is giving TX dislikers more ammunition. It's a stable product with constant support ofcourse ppl will blow things out of proportion for them

 

[smf]

I asked them about the potential for their software to brick the console if their software was corrupted in any way,

Even unmodified switches can brick, so yes.

If you start manually decrypting code and running it with a random stack, then also yes you can brick.

They obviously aren't going to answer a question on whether there is brick code in there and what can trigger it.

 

[Masacci0]

mmmhh ok

 

[Armadillo]

While I was around during the Wii era, I can't say I ever region changed a Korean console... Because why would I?

You're right though, I will say "it's different". First of all, that was 9 years ago, maybe try to find a more recent example? Second, that wasn't trying to brick everyone running homebrew, that was a very specific case that seems rather odd to me.

Funny that, bricking has a time limit on it that just happens to exclude the time Nintendo did it .

IIRC region changed korean were targetted as NA wiis were worth more in that region, so dodgy shops would buy korean wiis and then swap to NA and make more money. Also Korean wii is the only one that has a unique key, can't target the others the same way.

And what does it matter who it was targetting? End result is the end user has a brick.

Same old shit. Okay when Nintendo done it because "it was a long time ago" and "it only targetted X", so it's different.

 

[mustafag32g]

So they avoided the question and promoted their shit. Honestly I feel like this reply sums up why I can't stand these kinds of teams.

why cant you stand them? Because of their skills as hackers? They create a product and sell it, why your ass hurting ?? Its business, plus they owe you nothing so dont expect free stuff...

 

[Kioku]

If you are a regular user it shouldn't be a concern this brick code didn't surface until someone actually tried to tamper with it on dev level terms givien what info we have I'm not comparing or speculating on other things b/c they aren't TX. The open source community should be concerned b/c they are gonna have to look elsewhere or start from scratch. There's too much fear over 1 victim all its doing is giving TX dislikers more ammunition. It's a stable product with constant support ofcourse ppl will blow things out of proportion for them

This. The fear mongering is borderline pathetic here. This isn't Gateway. This wasn't an innocent system. Somebody messed around, knowing full well the potential consequences. Now, the community has turned it into a shit show with slander and baseless rumors.

 

[chrisrlink]

didn't MS do the same thing with JTAG'd 360's AND LOST a class action lawsuit?

 

[Batpeter]

there is no fiasco

 

[kamesenin888]

The community is always like that

 

[Kioku]

The community is always like that

Yeah, but it gets worse every generation.

 

[the_randomizer]

there is no fiasco

Nah, just blatant and blind white knighting sycophantic bullshit.

 

[TheDarkGreninja]

That was some first class avoidance right there.

 

[Batpeter]

it's like complaining you get shot when you try to steal from the mafia