ub3r1337's first impressions from a direct demo of TX upcoming new hardware mods!

ub3r1337 recently meet with TX to have them demo to him their upcoming new mods for the Switch (patched, mariko and lite). Unfortunately, he didn't get any pictures, but he says they'll be coming later on. Even so, he shared some of this new information at MaxConsole, also shown below:

First Off: It is a hardware mod. TX went back to its roots, and this solution is a device you need to install inside your Switch.

From what we could tell the install looks ultra simple and almost plug and play. When pushed about the install requirements, TX held back from claiming its fully solder-less, stating clearly that this particular design will always benefit from a few simple solder connections, versus the original intent of fully solder-less (at least for the classic model which is the unit we got to inspect).

In other words, a fully solder-less install is potentially possible with the classic models however it is not recommended by TX due to long term reliability concerns (we will cover this more in-depth at a later date, once we have our preview unit in our hands and put it thru some tests)

Second Point: There is one device for Patched and Mariko unit which is probably under production (see point three) and should be available soon They plan to release 2 devices; one for all classic versions (original, patch and mariko) and one for the Switch Lite.

Third Point: I really pushed for a release date, but TX refused to confirm anything during our meeting. From what I understood, even though it seems to be currently under production, because all sorts of things can occur in the factory during production, they will not commit to a date to me or their resellers until they are certain they can deliver on time enough stock to meet the demand.

I guess I can only respect that, this is probably why they did not announce anything yet, and we should know more once it is finally officially announced on their TX website.

At some point ub3r1337 hopes to get some pictures and videos from TX and a review unit, but we have no clue when that will happen. For now we just have to sit and wait for some more news regarding these new TX hardware mods to appear online!

Source: MaxConsole

 

[PatrickD85]

So this did not go any place it seems.
But I must say still props for the Autoloader though!

 

[ghjfdtg]

The people starting to call names again don't seem to understand. No one is saying this is undoubtedly fake (the previous news from the reseller was). You should take it with a grain of salt as long as it is not shown working (with a legit video unlike the last one which was proven fake because that was not an ipatched unit).

 

[Pipistrele]

God the baseless pessimsim regarding this being real is in the literal sense; insane. It's fueled by hatred. They've always delivered. Why would they lie now? The bias and hatred toward SX is ridiculous. It's like the shills find ONE thing, and then take even the tiniest thing and make it negative because they just hate SX. What childishness.

Grow up, guys. Jesus.

A team with already stained reputation making claims on a modchip in development without providing any actual info. It's not that people go out of their way to hate on SX (people are hyped for Mariko/Lite hack regardless of who will provide one) - skepticism is pretty justified here.

 

[Cakayx]

Im going to start to think its a real fale.. they Said end of the year..

 

[Josshy0125]

A team with already stained reputation making claims on a modchip in development without providing any actual info. It's not that people go out of their way to hate on SX (people are hyped for Mariko/Lite hack regardless of who will provide one) - skepticism is pretty justified here.

No its not. How is any of their reputation "stained"...? Only because youre salty that its paid only? Smh.

Who knows how they get the files for the exploit ..? Could even be theyre sold the exploit from the devs, or could even be part of the teams that find them. I mean they would make money and protect their privacy. Not to mention this happens every single time. Its kind of odd that one team finds a vulnerability, releases something to exploit the vulnerability, around the same time someone goes to release a paid version (ie gateway, sx, etc.). Im sure they pay the devs and they hand the shit over. Or are part of the team. Its a good way to get money and look good, from an individual standpoint, while protecting themselves.

But i digress. Youre literally going off of baseless pessimism. They wouldnt say theyve got something working just to fool people. Your bias is influencing your train of thought via irrationality.

 

[Pipistrele]

No its not. How is any of their reputation "stained"...? Only because youre salty that its paid only? Smh.

Alledgedly, they sell open source code, and they didn't really do much to refute the claims. Objectively, they inserted brick code into their firmware (a HUGE no-no for homebrew community) without telling anyone about it and denied responsibility for broken consoles. If that's not a stain on their reputation, I don't know what is.

Who knows how they get the files for the exploit ..?

We don't demand to know how they get files for the exploit - all we need is to see a working prototype, and until they actually deliver some footage of Mariko/Lite being hacked, their "WE'LL MAKE A MOD SOON WE PROMISE!" doesn't sound all that convincing.

They wouldnt say theyve got something working just to fool people.

If a company is willing to break consoles and ignore open source licenses, I don't see how they wouldn't hype people with fake product for cheap publicity boost.

 

[agpixel]

Let's esperate they will make an announcement for christmas

 

[Thekidpash]

Been following this for a while. It doesnt seem we'll be seeing something tangible soon... Any thoughts?

 

[Deleted User]

Nobody was ever bricked by that code except the person attempting to unpack sx os and it also didn't work as he successfully did unpack it without ruining his switch.

Also the emmc was not bricked, rather locked with a password which was also revealed.

That code hasn't existed inside sx os since sx os v1.2 anyway. This is a non-issue for anyone using sx os ever since. People just love to hate though. Digging up stuff from far in the past to attack TX right now.

 

[Essasetic]

Nobody was ever bricked by that code except the person attempting to unpack sx os and it also didn't work as he successfully did unpack it without ruining his switch.

Also the emmc was not bricked, rather locked with a password which was also revealed.

That code hasn't existed inside sx os since sx os v1.2 anyway. This is a non-issue for anyone using sx os ever since. People just love to hate though. Digging up stuff from far in the past to attack TX right now.

I mean yeah, but why was the brick code there to begin with? I'm not buying it was for a "hacker challenge".

 

[Draxzelex]

Nobody was ever bricked by that code except the person attempting to unpack sx os and it also didn't work as he successfully did unpack it without ruining his switch.

Also the emmc was not bricked, rather locked with a password which was also revealed.

That code hasn't existed inside sx os since sx os v1.2 anyway. This is a non-issue for anyone using sx os ever since. People just love to hate though. Digging up stuff from far in the past to attack TX right now.

It still does not change the fact that TX themselves decided to implement malicious code in their own homebrew. There were no good intentions by doing something like that which speaks a little about TX themselves. Very few programs out there have brick code out there and the most notable example Gateway. Without even drawing parallels, it definitely does not help TX's image. Imagine if word got out that a major developer implemented brick code in one of their products such as Nintendo or Microsoft? Sure the press would have a field day but public morale would plummet as not only would people trust the company less but the company also does not trust in their own product to an extent. You are indirectly defending brick code which is in of itself inexcusable. But this is all a discussion best reserved for another thread.

I don't get why people think this is fake just because there was no date. For the most part, developments in hacking and homebrew have never had dates. And the few times where dates were released, demands were not met in time which just led to frustration and disappointment. There was never a release date for SX OS, Atmosphere, or even Fusee Gelee but they all came out so why does this modchip require one to be legitimate? TX may have withheld the truth a couple of times but they have never outright lied.

 

[ghjfdtg]

Even if the brick code was "removed" it shows to which lengths they will go to protect what is mostly code taken and sold with zero credits. None of the original devs agreed they can use the code and the license requires providing the source code (Now someone will come with the argument again they are supporting piracy so it doesn't matter. That doesn't invalidate the fact they are violating licenses.).

 

[Josshy0125]

Nobody was ever bricked by that code except the person attempting to unpack sx os and it also didn't work as he successfully did unpack it without ruining his switch.

Also the emmc was not bricked, rather locked with a password which was also revealed.

That code hasn't existed inside sx os since sx os v1.2 anyway. This is a non-issue for anyone using sx os ever since. People just love to hate though. Digging up stuff from far in the past to attack TX right now.

Its like theyre trying to spin shit just to hate on it. Its childishness and immaturity. That's all it really is.

--------------------- MERGED ---------------------------

Even if the brick code was "removed" it shows to which lengths they will go to protect what is mostly code taken and sold with zero credits. None of the original devs agreed they can use the code and the license requires providing the source code (Now someone will come with the argument again they are supporting piracy so it doesn't matter. That doesn't invalidate the fact they are violating licenses.).

So how come both SX and Gateway somehow had the same "code" at literally the exact same time...? Thats the thing. Theyre probably selling the code to these companies to use them (or are part of the teams themselves), then releasing a free "pirate-less" alternative. They always pop up around the same time; there's very clearly a "deal" of some sort, or theyre part of the same teams. Who would work so fucking hard on an exploit, for nothing in return, monetarily...? And especially if one of these are the case *which im sure they are, this always happens so coincidentally*, why would they want the credit if they're trying to lay low as possible after selling the code, or connected to the teams in any way?

I think its ignorance from "the other side", assuming each and every time this happens - paid version coming out immediately when the free one does or is discovered - (which happens every single time btw) its the assumption that "its stolen code". This happens each and every time; too much to be a coincidence. I dont buy it. I think people here just like to hate on things. Theyre immature. Theyre children. Im sure theyre pirating for their atmosphere, as well. You cant hate on something if youre doing the same.

Again, its childishness.

 

[Armadillo]

ItImagine if word got out that a major developer implemented brick code in one of their products such as Nintendo or Microsoft? Sure the press would have a field day but public morale would plummet as not only would people trust the company less but the company also does not trust in their own product to an extent. You are indirectly defending brick code which is in of itself inexcusable. But this is all a discussion best reserved for another thread.

Nintendo did. They intentionally bricked region changed korean wii's. Press didn't care and the same people that complain about gateway and xecuter handwaved it away with various excuses.

 

[Kubas_inko]

Nintendo did. They intentionally bricked region changed korean wii's. Press didn't care and the same people that complain about gateway and xecuter handwaved it away with various excuses.

Was that automatic (as soon as you region changed it bricked) or manual (somehow)?

 

[Armadillo]

Was that automatic (as soon as you region xhanged it bricked) or manual?

It was when you updated to whatever system update had the check.

I can't remember what update. But it specifically checked for the Korean key and if it found it, bent you over and shafted you.

It wasn't just an incompatiblity, it was a specific, programmed check. Look for the Korean key and if found, brick and give you an error code. Nintendo could have just made the update fail and say "modified system etc", but chose to shaft you with a brick instead.

 

[ghjfdtg]

Never owned a Wii but no matter who does it there is no excuse to bricking devices you don't own. As far as i heard what happened with the korean Wii's was not deliberately but a bug. Can't say for sure.

 

[Kubas_inko]

It was when you updated to whatever system update had the check.

I can't remember what update. But it specifically checked for the Korean key and if it found it, bent you over and shafted you.

It wasn't just an incompatiblity, it was a specific, programmed check. Look for the Korean key and if found, brick and give you an error code. Nintendo could have just made the update fail and say "modified system etc", but chose to shaft you with a brick instead.

Uh oh.
That's kinda illegal, but who is gonna fight Ninty, right?

 

[Armadillo]

Never owned a Wii but no matter who does it there is no excuse to bricking devices you don't own. As far as i heard what happened with the korean Wii's was not deliberately but a bug. Can't say for sure.

Not a bug.

https://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."

100% intentional.

Encrypt with Korean key, if it matches, get fucked.

 

[Keylogger]

It still does not change the fact that TX themselves decided to implement malicious code in their own homebrew. There were no good intentions by doing something like that which speaks a little about TX themselves. Very few programs out there have brick code out there and the most notable example Gateway. Without even drawing parallels, it definitely does not help TX's image. Imagine if word got out that a major developer implemented brick code in one of their products such as Nintendo or Microsoft? Sure the press would have a field day but public morale would plummet as not only would people trust the company less but the company also does not trust in their own product to an extent. You are indirectly defending brick code which is in of itself inexcusable. But this is all a discussion best reserved for another thread.

I don't get why people think this is fake just because there was no date. For the most part, developments in hacking and homebrew have never had dates. And the few times where dates were released, demands were not met in time which just led to frustration and disappointment. There was never a release date for SX OS, Atmosphere, or even Fusee Gelee but they all came out so why does this modchip require one to be legitimate? TX may have withheld the truth a couple of times but they have never outright lied.

Brick code is here only to prevent from copy
If you don’t touch their code, you don’t need to worry about the brick code