its not there code they stole it 1st.don't fuck with team X trying to steal their code and you won't get bricked!
what you were trying to say is don't try to steal the code they stole and you won't get bricked.
its not there code they stole it 1st.don't fuck with team X trying to steal their code and you won't get bricked!
Scientists often present snippets of their work (all as work keeping people updated on work they're doing at the moment) at conferences before their work is published in journals.A respected scientist would never publish a headline first and then tell people to wait for his paper to be published. It will always be publish the paper first.
Scientists often present snippets of their work (all as work keeping people updated on work they're doing at the moment) at conferences before their work is published in journals.
I would've preferred this thread to just be a list of things to avoid doing to mitigate the risk as much as possible. It's not very helpful if the only advice is don't buy TX stuff, especially when no regular user has even experienced a brick it will be hard to convince people of anything. Kinda like when bans were predicted and no one really listened until the wave actually started.
I feel that this is an assumption and there could be circumstances, however rare, that could cause issues. I'd like to think one could simply contact TX and get it resolved, but if they then accuse the customer of tampering then that presents a sticky situation.Don’t try to tamper with it and you’ll be fine
No one ever said anything about stealing games. What's absolutely abhorrent is the "us vs. them" mentality TX fanboys have been showcasing ever since it came out. Decrying legitimate, non-partisan informational tweets and writeups on the pretense of "THEY'RE TRYING TO TAKE THE FREE GAMES AWAY FROM US" is just missing the point altogether.stealing code from other devs .... that's bad real bad!
but stealing games ... sure no problem nothing wrong with that though.
Good luck having your Switch bricked when SX pushes a faulty update to their OS. More likely to happen than not.
quote.this guy needs to let it go. no one cares. and nothing is going to happen to anyone's switch.
No one ever said anything about stealing games. What's absolutely abhorrent is the "us vs. them" mentality TX fanboys have been showcasing ever since it came out. Decrying legitimate, non-partisan informational tweets and writeups on the pretense of "THEY'RE TRYING TO TAKE THE FREE GAMES AWAY FROM US" is just missing the point altogether.
Putting brick code in several parts of your CFW isn't "defending your hard work", it's being scornful and only serves as a threat to developers trying to RE their CFW.
Stealing parts of open source code without attribution isn't "giving the community what they want" or "okay because it's open source, so that makes it okay to steal", it's leeching off the community's work.
You can use SX OS if you want, but adamantly trying to defend and justify their actions when the only thing they're after is lining their own pockets and undermining the rest of the community to maximize their profits is repugnant.
Totally disagree. They've stolen code and implanted malicious content into it and are now selling it for a profit. They are in violation of tons of licence agreements for said code. They are dancing around the subject and giving nothing answeres. (Also brick code does indeed accidently trigger.... This is fact....) If you want to keep using possibly damaging software feel free I'll simply use the open source puplic tools that are known to be free of malicious content. Of course I never intended to buy anything from this group when I found out it's not even the original xecuter crew. Surprised they even actually delivered a real product..... Albiet loaded with stolen and malicious code...this guy needs to let it go. no one cares. and nothing is going to happen to anyone's switch.
Functional product based on stolen work*yes but complaining and fear mongering is not helping the community. if devs truly want to help those who have yet to purchase SX OS, then come up with an alternative solution.
instead of spending time trying to crack SX OS, why not develop your own loader? if that is too hard, then you have to give TX credit.
they are the first to come up with a functional product and therefore it is their choice to do whatever they want, no matter how reprehensible their actions are.
They are in violation of tons of licence agreements for said code.
I fell the same way if i knew all of this before i payed for my key i would not have payed for it and would have waited longer for the free stuff, But I did get the code and it does let me play my games so because i payed for it sadly i'm gonna use it although i'm gonna hold off on any updates that they come out with to make sere there is no bricks from a miss trigger though.Totally disagree. They've stolen code and implanted malicious content into it and are now selling it for a profit. They are in violation of tons of licence agreements for said code. They are dancing around the subject and giving nothing answeres. (Also brick code does indeed accidently trigger.... This is fact....) If you want to keep using possibly damaging software feel free I'll simply use the open source puplic tools that are known to be free of malicious content. Of course I never intended to buy anything from this group when I found out it's not even the original xecuter crew. Surprised they even actually delivered a real product..... Albiet loaded with stolen and malicious code...
--------------------- MERGED ---------------------------
Functional product based on stolen work*
I did not ever think of that but yes that is true they can push an update out that would trigger it as soon as you boot the cfw.Good, let's assume that the brick code exists, that the normal user is not able to run it accidentally. Can the next system update from Nintendo do this? Can new firmware from Nintendo modify the SX so that it "thinks" that it is a hacking attempt and will crash the system?
Same pointIf i were Nintendo i would try to trigger that self destruct code when a modified Console gets detected
So, having such a Timebomb/bricking code in a "Product" could not be discussed, nor accepted.
Shame on TX
WANNA PLAY :)