Hacking Tx's Official Response to SX Bricking Code

[The Catboy]

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

Honestly this is apples to oranges. I don't think Nintendo actually intended to brick wiis, I think that was the result of poor testing. Nintendo never repeated this again, despite having several chances to do so. This is an actual brick code that is intended to brick a system if the user messes with Tx's code. They both brick, but one is actually malicious where the other was just stupid.

 

[Kioku]

Honestly this is apples to oranges. I don't think Nintendo actually intended to brick wiis, I think that was the result of poor testing. Nintendo never repeated this again, despite having several chances to do so. This is an actual brick code that is intended to brick a system if the user messes with Tx's code. They both brick, but one is actually malicious where the other was just stupid.

Nintendo never repeated their bricks after facing such retaliation and backlash? I'm SHOCKED! SHOCKED I TELL YOU!

 

[TheDarkGreninja]

Can someone give me a quick low down on what happened with Nintendo and region changed Wiis?

 

[The Catboy]

Nintendo never repeated their bricks after facing such retaliation and backlash? I'm SHOCKED! SHOCKED I TELL YOU!

What I am trying to say is that it looks like Nintendo learned from that and didn't repeat it. Nintendo could have actually made an update that looked for the FIRM0/1 protection and removed A9LH. This update would have removed A9LH from an old3DS without hassle, but bricked the new3DS. This update would have also had a risk of bricking clean systems. It seems like Nintendo was aware of this and never pushed out such an update. Nintendo learned from their mistakes and haven't repeated them as of the previous system. So yeah, not really shocking that Nintendo won't want to brick systems again, but I brought up that they didn't repeat it as a means of saying that it's not really the same situation as the brick code.

Can someone give me a quick low down on what happened with Nintendo and region changed Wiis?

In an attempt to remove homebrew from the Wii, Nintendo pushed out the update 4.2 for the Wii. This update made changes to the boot2 and resulted in several wiis (hacked and clean) being bricked as a result. Basically Nintendo updated files that they shouldn't have updated in such a manor and it resulted in bricks.

 

[TheDarkGreninja]

What I am trying to say is that it looks like Nintendo learned from that and didn't repeat it. Nintendo could have actually made an update that looked for the FIRM0/1 protection and removed A9LH. This update would have removed A9LH from an old3DS without hassle, but bricked the new3DS. This update would have also had a risk of bricking clean systems. It seems like Nintendo was aware of this and never pushed out such an update. Nintendo learned from their mistakes and haven't repeated them as of the previous system. So yeah, not really shocking that Nintendo won't want to brick systems again, but I brought up that they didn't repeat it as a means of saying that it's not really the same situation as the brick code.

In an attempt to remove homebrew from the Wii, Nintendo pushed out the update 4.2 for the Wii. This update made changes to the boot2 and resulted in several wiis (hacked and clean) being bricked as a result. Basically Nintendo updated files that they shouldn't have updated in such a manor and it resulted in bricks.

Ah, I remember reading about that a while back (Probably 10 years ago now Lmao)
It definitely would've been something I would've chastised Nintendo for at the time as I have done with TX, but I'm not going to hate on a company that, as you rightly say, has learned from their mistake.

 

[Armadillo]

In an attempt to remove homebrew from the Wii, Nintendo pushed out the update 4.2 for the Wii. This update made changes to the boot2 and resulted in several wiis (hacked and clean) being bricked as a result. Basically Nintendo updated files that they shouldn't have updated in such a manor and it resulted in bricks.

It was straight up checking for the korean key and then bricking if found.

Shit was no "accident".

http://wiibrew.org/wiki/Error_003

"IOS tries to encrypt a certain byte pattern with the Korean key and then compares it with hard coded values, if the result matches it returns 0 which will then trigger the error in the System Menu." Try to encrypt with the korean key, compare it and if it matches brick you with the 003 error.

Intentional as you can get. Not trying to get "rid of hombrew". Straight up checking to see if it's been region changed and then brick if it has.

Mental gymnastics in full swing for Nintendo doing it.

 

[Drakia]

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

Why yes, yes I can:
https://twitter.com/hexkyz/status/1012146388484755456

 

[kamesenin888]

Why yes, yes I can:
https://twitter.com/hexkyz/status/1012146388484755456

Thats the homebrew launcher, I give you that they used the community one, but that is not most of their work? or is it like you claimed? also I am doubting of this dude hekxys it seems he has a personal vendetta to TX, he even admitted he hated it, it could be a lie, but only time will tell with our piracy enabler hackers, gambare!!

thanks hekxys for cracking the code and naehwer for helping with the tools for delivering free efficient piracy to all

 

[FliP0x]

That's the promotion, but they completely avoided the actual topic on hand. They aren't addressing the actual brick code that they built into their product, which is the concerning issue. Everyone knows (or should know) that hacking your system runs the risk of bricking it, but deliberately bricking someone's system for trying to mess with your code is a completely different issue.

Not defending anyone, I just can't agree with your point of view

Should they have said "Our product is safe, but you don't have to buy it"?

About the brick code, it is clear what it does and when it does it. It's a security mechanism for TX to not get their work stolen and copied.

If you developed a product, would you let people use it for free?

 

[Drakia]

Not defending anyone, I just can't agree with your point of view

Should they have said "Our product is safe, but you don't have to buy it"?

About the brick code, it is clear what it does and when it does it. It's a security mechanism for TX to not get their work stolen and copied.

If you developed a product, would you let people use it for free?

Ironic considering their "product" is based off of the communities research and code

 

[Deleted User]

I've been saying for months now that TX might do a Team Gateway. It seems I was right. But nobody uses Gateway anymore. It fell out of popularity when free solutions which were better became available.

TX OS won't last long because it wont be able to compete with atmosphere or Reisyukaku's CFW.

EDIT: Apparently Layered FS loads games faster than SX OS already.

 

[cearp]

I've been saying for months now that TX might do a Team Gateway. It seems I was right. But nobody uses Gateway anymore. It fell out of popularity when free solutions which were better became available.

TX OS won't last long because it wont be able to compete with atmosphere or Reisyukaku's CFW.

I don't think anyone thought there wouldn't be brick code.
Whatever free solutions emerge, I hope they can use xci files, because that's useful. I don't think there is a non gw way to use .3ds files right?

 

[subcon959]

Has anyone actually verified any of this or is everyone blindly believing this one guy?

 

[Dabiolos]

Ironic considering their "product" is based off of the communities research and code

yeah looks like they "borrowed" the homebrew launcher from the community but on the other side you can use it without license. They should have credited this part of sx where credit belongs to.

Since their HB-Launcher is less compatible with current homebrews there is a chance this is because of DRM measurements taken. Maybe a DRM free sx would run faster and better...

Their product is the backup launcher which is what you need the license for.

 

[FliP0x]

Ironic considering their "product" is based off of the communities research and code

If that is so, then why does the community try to crack SX OS if all TX did was use what the community researched and released?

 

[Drakia]

If that is so, then why does the community try to crack SX OS if all TX did was use what the community researched and released?

The people trying to Reverse Engineer SXOS aren't doing it to "crack it", they are doing it for the same reason they RE'd the Switch in the first place, a challenge.

https://twitter.com/hexkyz/status/1012362983572492291

 

[tides]

gateway said support for life too

until they disappeared

it is clear that they are taking a page out of gateway, fucking people who crack their os even harder. or maybe they are gateway. we don't know.

anyway they are no different from nintendo IMO.

nintendo brick your device by shorting it if you buy 3rd party accessories. tx brick your device if u crack their software.

not sure which one is worse.

 

[FliP0x]

Sure, then they will have to face the challenge and circumvent the brick code and not cry on here once their switches get bricked.

But hey, that will be an even harder challenge to get them unbricked.

EDIT:

It just struck me, why would the community reverse engineer something they have already researched and released?

/insert meme
*already posted it, won't post it twice*

 

[Drakia]

Sure, then they will have to face the challenge and circumvent the brick code and not cry on here once their switches get bricked.

But hey, that will be an even harder challenge to get them unbricked.

EDIT:

It just struck me, why would the community reverse engineer something they have already researched and released?

/insert meme
*already posted it, won't post it twice*

The people _actually_ doing the work on this know how to unbrick their console, hexkyz isn't some newbie who just got into the scene. And the challenge is of course to get past SXOS's protection, like how can you not realize that? You're not a very smart guy.

 

[Benoit934]

The people _actually_ doing the work on this know how to unbrick their console, hexkyz isn't some newbie who just got into the scene. And the challenge is of course to get past SXOS's protection, like how can you not realize that? You're not a very smart guy.

When I hacked the TI Nspire boot2 some stated (hard to translate) this :

But I find it amusing that someone who could have largely been happy with nLaunch work hard to make a "free-boot 2", just because he wanted to and because it was "neat".

Just saying hackers are weird they can work hundred hours on something just because they want something and there is no others explanation (yes some just want money but others are addicts and feel the urge to break security checks or control their lights with a TV remote)

Basically they tend to enjoy doing random stuff and in many cases it's just useless (afterall when you play video games and try to get best score it's useless and you spend countless hours playing to reach that goal ...)