"You" in my post also wasn't directed to you specifically as well. I'm speaking in general.
Nintendo themselves released a update (that supposedly.) which bricked Switches. I'm not sure if people are that afraid anymore.
That's the way to tackle all the people that want backups that dont care what a biased dev says, go for it champ
You just said "Wasn't caused by an update", then said, "Stuff like that been happening since 3.0". This means an update caused it. Also, got proof it was happening since 3.0? That seems quite specific.
I fail to see how noting that occurrences existed before 5.0 implies that an update still caused it. 3.0 is merely an example.
Plus, it's not like any third party docks existed when 2.0 and below was a thing. But given that the issue is in the USB-C port and microprocessor unit and not the console's firmware...
EDIT: https://www.reddit.com/r/NintendoSw...did_someone_brick_their_switch_using_a_third/ --- all the way back in 2017. 5.0.0 released in March 13, 2018. The thread was created seven months ago in December. Point of the matter, Nintendo bricking users is a false statement. It is a hardware issue, not software related.
Second link: http://www.trustedreviews.com/news/nyko-portable-docking-kit-breaks-nintendo-switch-3315442 - October 2017
Last edited by Halvorsen,
False. That was caused by the Switch needing USB-A to USB-C cables with the 56k ohm resistor in them, and people using cables without them in there. If you don't believe me, Google it. All Nintendo official cables have them in there, and Nintendo released an official 3rd party list with cables that have them in there. Plus, if Nintendo really did brick your Switch with an update, they'd repair it. SX won't and Nintendo won't repair one used with SX OS.
Not a single user has been affected by any bricks regarding TX while using their firmware as it's intended to be used. Clearly this guy's ego is plummeting since it's clear that he can't crack the SX OS, and the farther he digs the more booby traps he discovers.
To put it short, if you don't want to get bricked by TX, don't mess with their OS beyond what they're currently offering.
To put it short, if you don't want to get bricked by TX, don't mess with their OS beyond what they're currently offering.
I just realized, why are people bitching about bricking code when they're buying a device that will allow them to mess with Nintendo's closed source code? Aren't people that are mainly buying this for pirating? Why should you be so protected when you're stealing shit?
Probably because if (and this is a big IF) SX OS bricks a Switch, TX is punishing whomever for owning a Switch rather than for its intended purpose which is to deter hacking. Theoretically, something like a self-destruct button for the code itself would work better for what TX is trying to do with their brick code, but its a risk they are willing to take to protect their product.
Last edited by Draxzelex,
- Joined
- Mar 31, 2008
- Messages
- 103
- Trophies
- 0
- Age
- 74
- Location
- Charlotte, North Carolina
- Website
- en.wikipedia.org
- XP
- 618
- Country
-
Some TX haters are spreading fear around here. An element of truth, and a huge amount of speculation with words like “WILL” being used as if they are predicting the future.
LMAO - Chill, relax and use the homebrew solution that these same TX haters said would be released. Personally, I hope it is soon.
LMAO - Chill, relax and use the homebrew solution that these same TX haters said would be released. Personally, I hope it is soon.
Last edited by ghorricks,
D
Deleted User
Guest
Considering it was apparently "easy" to implement, SciresM and a few more of the leading devs should have seen the bigger picture and should have worked on releasing a backup loader themselves ahead of SX OS' release date.
I know this certainly goes against their morals and principles, but they could have at least damaged TX's SX OS sales.
Surely most people who are waiting for a free backup loader solution will never buy SX OS anyway and a portion if not a majority of people in the piracy scene who have already bought SX OS would probably have cancelled their order knowing their was already a free solution released.
It seems like these developers are just upset because their work is being used for the wrong reasons, but let's be honest.. which console in the past 20 years that has been exploited hasn't eventually had a backup loader?
What exactly did these devs think would happen? Let's face it, people like free stuff and piracy is bound to happen when you exploit a console, especially when you're exploiting a hardware level flaw.
I'm neither for or against TX or any of the developers on this scene as I think competition is always good for any homebrew/hacking scene. Just stating what I would have done if I were in their shoes and had their skills.
I certainly wouldn't be salty about this, that's for sure..
I know this certainly goes against their morals and principles, but they could have at least damaged TX's SX OS sales.
Surely most people who are waiting for a free backup loader solution will never buy SX OS anyway and a portion if not a majority of people in the piracy scene who have already bought SX OS would probably have cancelled their order knowing their was already a free solution released.
It seems like these developers are just upset because their work is being used for the wrong reasons, but let's be honest.. which console in the past 20 years that has been exploited hasn't eventually had a backup loader?
What exactly did these devs think would happen? Let's face it, people like free stuff and piracy is bound to happen when you exploit a console, especially when you're exploiting a hardware level flaw.
I'm neither for or against TX or any of the developers on this scene as I think competition is always good for any homebrew/hacking scene. Just stating what I would have done if I were in their shoes and had their skills.
I certainly wouldn't be salty about this, that's for sure..
Last edited by ,
I agree. I guess Nintendo should be the one punishing. Game Consoles creators should just brick consoles instead of banning them. That's how you deter hacking real damn well. People will just go buy a new one anyways. Like video game accounts. Got banned in a pay to play game? That person will just go buy a new copy anyways. Maybe multiple times over. Like those video game cafes, which get games free, and why hackers are rampant there but once they need to pay for it, then the hacking stops real quick.
tl;dr: Nintendo should brick consoles instead of banning them.
Don’t tamper with shit you have to buy for €25-40 which saves you €x00’s. If you tamper with it, be prepared to throw your €300 switch out of the window 
D
Deleted User
Guest
Why are any of you OK with code that intentionally bricks your Switch being in a product you use, even if you aren't likely to trigger it?
I would not feel safe running a program that even contains bricking code because it could be triggered by a bug.
Yes, it's SUPPOSED to only be triggered if you crack it but we all know what happened with Gateway.
Also I would never use a product that contained bricking code on principle - blocking the use of your own product if it's pirated is fine, but bricking the device it's on is just immoral. Imagine if Windows erased the BIOS chip if it detected it was pirated...
I would not feel safe running a program that even contains bricking code because it could be triggered by a bug.
Yes, it's SUPPOSED to only be triggered if you crack it but we all know what happened with Gateway.
Also I would never use a product that contained bricking code on principle - blocking the use of your own product if it's pirated is fine, but bricking the device it's on is just immoral. Imagine if Windows erased the BIOS chip if it detected it was pirated...
Similar threads
- No one is chatting at the moment.
