Hacking SX Brickcode is Worse Than Expected, Can Trigger From Use

[Red1Reaper]

This, right here, is a prime example of why people need to read EVERYTHING. No reported bricks outside of Hex. Chances of there being any in the near future is slim, unless you decided to dive into the code, then it's user error.

Still is good to know of the posibility, to encourage users to do backups even more and to have procedures of restore prepared in the case a final user has the bad luck to trigger it sometime in the future.

 

[Kioku]

Still is good to know of the posibility, to encourage users to do backups even more and to have procedures of restore prepared in the case a final user has the bad luck to trigger it sometime in the future.

That's a given. Backups should be the first thing you do prior to loading new CFW, updates (if no efuses are burnt and we can bypass this). I've no issue with saying what MAY happen. However, there's too much misinformation going on.

 

[Batpeter]

Title is misleading IMO. Hex says it can be triggered by accident. As he does not define the context i assume by accident when messing around with the files. Or, by CPU error but those changes are so slim you might as well live underground so you won't get hit by a meteorite.

 

[CyberSardinha]

First we know that's always a risk of bricking our system as any encryption in any software... the risk is 100x when you try to bypass stuff that is not supposed to be bypassed in normal use. I would like to know how can that be triggered in normal use... that would be great info so that we can try not to have any problem... But the way that he said looks more like he is stuck on his hack and can't bypass the security safely and all this is only elbow pain. that happens when people say more than they can achieve.

 

[Essasetic]

It's very unlikely it's going to be bricked through normal use. Even then it's only through changing voltages and other things like that. Calm down everyone!

 

[P4RI4H]

Boot locker password seems to be "WANNA PLAY? ":

sneak peek of TX trying to brick my emulator, *oh noes*! (in case anyone bricks while messing with this the password should usually be "WANNA PLAY? :)") pic.twitter.com/vKaPyY5GpM

— naehrwert (@naehrwert) June 28, 2018

 

[Essasetic]

Boot locker password seems to be "WANNA PLAY? ": https://twitter.com/naehrwert/status/1012153818212003840?s=09

Dude... Nobody cares (except for the people who want a crack).

 

[Der_Blockbuster]

The font is too small, can you make it bigger?

Sorry, I pasted the Title and it automatically kept the size of the font.

 

[Localhorst86]

It killed off the r4i/orange 3ds and whatever the other one was.

Don't have to like it, but it did stop the cloning when it was added.

It might have killed only the clone flashcards in an earlier version. In a later version they bricked the 3ds instead.
The outcome was that it did stop the cloning, yes. But simply refusing to work on these clones would have had pretty much the same effect. There was never a need to brick the clone devices or even the console itself.

 

[Taffy]

...see this is why I stopped caring and left to go to r/nerf.

also hi I'm back from a hiatus. What'd I miss?

 

[kamesenin888]

It might have killed only the clone flashcards in an earlier version. In a later version they bricked the 3ds instead.
The outcome was that it did stop the cloning, yes. But simply refusing to work on these clones would have had pretty much the same effect. There was never a need to brick the clone devices or even the console itself.

You were not in those times, they tried killing it but the clones bypassed that like 2-3 times, the bricks stopped them completely

 

[tivu100]

It's very unlikely it's going to be bricked through normal use. Even then it's only through changing voltages and other things like that. Calm down everyone!

- The code can indeed trigger with normal usage, but the odds are so low that is very unlikely that anyone will be affected by this (unless you're messing with voltage or time sensitive stuff);
- These were direct observations from reverse engineering and testing their code.

— Mike Heskin (@hexkyz) June 25, 2018

The irony is over 9000. Repeat what certain person said as fact (voltage blah blah blah), but wouldn't care less about new discovery from extra research by same person.

Where else did the community get that info? TX themselves haven't responded while their support dodged the question

 

[Localhorst86]

You were not in those times, they tried killing it but the clones bypassed that like 2-3 times, the bricks stopped them completely

Then your code is not 100% reliable. If your code is not 100% reliable in detecting clones, you shouldn't have the code brick devices.

 

[MasterJ360]

I will never understand of the replies here. People hack things for RESEARCH.
That comes in the form of personal research, open-source research, and bragging-rights research.
Why would you NOT want to know that there was bricking code provided in the SX software?
Genuinely, why does having that knowledge enrage you so much? Is it because you paid for it? Is it because you think TX is infallible? Blame the Russians?

Half of the replies here don't answer what it is that you're so against and instead comment on everything but the fact, and it is fact, that there is code in there that MAY or WILL affect a subset of users.
You all seem to think because a widespread bricking situation hasn't arisen, that there won't be some home-brew released in the future that will act like a virus that will specifically "turn-on" the brick code mechanism.
Oh, but you all will know immediately. "People will report it!"
Well, no, there are several obfuscation methods to brick at random times or for random scenarios.
and of course when that happens to you - you're all going to be looking for developers like @hexkyz to figure out what went wrong.

The reason for trying to crack SXOS is obvious. To see how it works. Knowledge.
Stop using anything developed by people who learn how the software works to create other applications that take advantage of the same methods.
If you aren't a developer, if you aren't creating home-brew, and specifically if you're just a wide-mouthed GBAtemp member spewing your opinion
on what other developers should or should not do based on the fact that YOU don't like the fact that someone else wants to know how something works - don't use any of it!
It's simple. Oh, but ego. Oh, but piracy.

Okay, just because you're saying what you think people shouldn't be doing based on your morals, they're totally not going to do it.
So many of you have logical fallacy arguments that it just hurts my brains.

Why even comment on these threads when you want no involvement?
You're creating spam and drama and NO ONE WANTS IT. Get out, OUT! Thanks.

B/c threads like this are nothing more but fear mongering [drama] from a failed crack. Research is great, but we still lack huge amount of evidence that this brick code can affect anyone there are things that "Could" possibly trigger it, but the % of that possibility is still very unknown the only thing we have gathered from this is that any attempt to modify boot file will cause a brick code. That's what Hexkyz needs to own up instead of trying to give a reason to not buy a non open source product that he failed to crack on. Devs can have big ego's and they do not not like to be outsmarted in the eyes of the public media. At this rate Hexkyz just wants to be praised for finding a brick code which is less likely to trigger to a regular user b/c we have 0 interest in tweeking what we paid for. I'll believe Hexkyz when regular users get bricked, but right now he's just a wolf howling at the moon

 

[Nincompoopdo]

This looks like a disgruntled sore loser trying to pick a fight. TX won the race, they delivered the product on time as promised... but Atmosphere made no progress.

If TX stole their code as they claimed then why can't they - using their own code delivered the same result?

 

[the_randomizer]

Oh, an even more fiercely thickening plot, I see. I'm not surprised, but I'm even less surprised by the blind, sycophantic damage control warriors as usual.

I'm sorry, but if you use this, or any CFW as well as backups, and go online and then get your console banned, why do you even bother asking for sympathy? You knew the risks,
you know what you were getting into, who are you to bitch and moan about it?

I hope Team TX's OS gets cracked and the DRM fully removed.

 

[Goloki]

Oh, an even more fiercely thickening plot, I see. I'm not surprised, but I'm even less surprised by the blind, sycophantic damage control warriors as usual.

I'm sorry, but if you use this, or any CFW as well as backups, and go online and then get your console banned, why do you even bother asking for sympathy? You knew the risks,
you know what you were getting into, who are you to bitch and moan about it?

I hope Team TX's OS gets cracked and the DRM fully removed.

This has nothing to do with getting banned for using TX OS, but OK. You showed them!

 

[DKB]

This has nothing to do with getting banned for using TX OS, but OK. You showed them!

Same shit, he's basically saying that if you fuck with someones code with the intent to steal it, don't be surprised when you get fucked (Bricked.).

 

[the_randomizer]

This has nothing to do with getting banned for using TX OS, but OK. You showed them!

Told you people would be quick to defend Team TX for putting their dickish brick code/DRM into their own product lol. People sure love defending them.

Why is it so bloody hard for people to grasp this?

 

[jakkal]

Still enjoying my sx pro
I wanted backup loading and I got what I paid for.