Hacking Tx's Official Response to SX Bricking Code

[Drakia]

You won't convince me otherwise.
You're trying to hard buddy

Here you go, some light reading: http://hexkyz.blogspot.com/2018/06/chill-shills.html

Never trust a company that puts malicious code in their product.

 

[Ra1d]

You won't convince me otherwise.
You're trying to hard buddy

Only 2 people were affected by Brickway, and Gateway even replaced their consoles. Everything else is drama and propaganda.

 

[the_randomizer]

Ooh, PR damage control bullshit, tell me more. Wow, this definitely makes me want to buy their products, alright.

 

[Drakia]

yeah well, i used an example earlier, it's like protecting your drug den with guns.
it's not a surprise, if you mess with something 'shady' (tx), you get in trouble.

nintendo's a real, accountable company (unlike tx), and would get in big trouble if they bricked people.
but tx - it's different.

I don't disagree, TX is shady shit, but that's why I won't buy from them. I was on the fence about it, but now that I know their software has brick code, it's off the table, even if I would never in a million years hit it.

 

[xiaNaix]

Here you go, some light reading: http://hexkyz.blogspot.com/2018/06/chill-shills.html

Never trust a company that puts malicious code in their product.

By his own admission this supposed "malicious code" would only be triggered by voltage or timing attacks.

 

[RedHunter]

Here you go, some light reading: http://hexkyz.blogspot.com/2018/06/chill-shills.html

Never trust a company that puts malicious code in their product.

Well it's not their fault is the community sucks so much that instead of making their own free cfw they try to steal other people ones.

 

[MasterJ360]

So you want them to explain why there's a brick code to hackers trying exploit something they are making tons of money off of? So TX is shady when its a dead end to opensource? Can yall stop hating please?

 

[jramirex]

This is how starts. They put a brick code now and say don't worry it's safe. Until it isn't.

TX did not need to put that there, brick codes only lead to bricked consoles including from legit costumers.

 

[KTroopA]

nice bullet dodge by TX..

 

[Drakia]

By his own admission this supposed "malicious code" would only be triggered by voltage or timing attacks.

> watches over the overall execution time of this payload

It watches the overall exec time. So what if your Switch is really hot and CPU-throttled?

Well it's not their fault is the community sucks so much that instead of making their own free cfw they try to steal other people ones.

You mean the community they probably stole most of their work from? That one?

 

[kamesenin888]

> watches over the overall execution time of this payload

It watches the overall exec time. So what if your Switch is really hot and CPU-throttled?


You mean the community they probably stole most of their work from? That one?

You really are a assmosphere fan, prove that they stole work? Can you?

 

[Drakia]

You really are a assmosphere fan, prove that they stole work? Can you?

You think TX would have anything without Switchbrew to use as a resource, and Hekate/Atmosphere to look at implementation for? When was their first announcement for it, beginning of May? After a year of the community reverse engineering the Switch, and finding the RCM exploit that TX ended up using.

Shit, I made stuff for 3DS based off other peoples work, I ported the Atmosphere FS-Mitm kernel patch to Hekate, I don't know shit on writing any of this myself, console RE is complicated. But I sure as hell give credit when I do it.

 

[Rel]

I don't disagree, TX is shady shit, but that's why I won't buy from them. I was on the fence about it, but now that I know their software has brick code, it's off the table, even if I would never in a million years hit it.

I guess you'll never support Nintendo as well since they had brick code back on the Wii.

 

[cearp]

By his own admission this supposed "malicious code" would only be triggered by voltage or timing attacks.

eh not really - "In theory, it should be really difficult for this mechanism to trigger at random, but it is possible. The performance monitor features of the CPU are prone to mistakes just like anything else."

 

[The Real Jdbye]

I asked them about the potential for their software to brick the console if their software was corrupted in any way, and if they could offer a way to unbrick it if it was mistakenly done.

If everyone remembers, Gateway had a problem with their boot.dat. If it were corrupted in any way, it'd brick. Even if it wasn't you screwing with it.

So yeah, they definitely avoided the question.

Worse, it could be consistently triggered by the diagnostics check even on a non-corrupted launcher.dat file. It was seriously glitchy. Hopefully nothing like that ever happens with SX.

 

[kamesenin888]

You think TX would have anything without Switchbrew to use as a resource, and Hekate/Atmosphere to look at implementation for? When was their first announcement for it, beginning of May? After a year of the community reverse engineering the Switch, and finding the RCM exploit that TX ended up using.

Shit, I made stuff for 3DS based off other peoples work, I ported the Atmosphere FS-Mitm kernel patch to Hekate, I don't know shit on writing any of this myself, console RE is complicated. But I sure as hell give credit when I do it.

Well you cannot prove it, tx announced their work earlier than reswitched's in reality it works better and it's stable, atmosphere is not nearly finished, it doesnt work as intented

 

[The Catboy]

So you want them to explain why there's a brick code to hackers trying exploit something they are making tons of money off of? So TX is shady when its a dead end to opensource? Can yall stop hating please?

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.

Well it's not their fault is the community sucks so much that instead of making their own free cfw they try to steal other people ones.

You mean like this free CFW that already exist? This one right here? That free CFW, that already exist, and is open source. Reverse engineering their code isn't theft and he's not trying to "steal their code." He's trying to reverse engineer their closed-source code because he wants to, that's just something he does.

 

[cearp]

what is 'official' about this response the OP got anyway?
it's just an email, it's only an official response if they deem it so. (right?)

Worse, it could be consistently triggered by the diagnostics check even on a non-corrupted launcher.dat file. It was seriously glitchy. Hopefully nothing like that ever happens with SX.

yes it was terrible but they fixed it.

anyway, i don't want to seem like a shill

brick code isn't nice, if it bricks the wrong people.

 

[The Real Jdbye]

I guess you'll never support Nintendo as well since they had brick code back on the Wii.

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.

 

[mansonss]

what is 'official' about this response the OP got anyway?
it's just an email, it's only an official response if they deem it so. (right?)

I called it official because it came directly from them. This is what they have to say about it (as of right now.)