I believe him but would still like to see the exact question he asked.OP asked them I believe, gave a really basic answer.
I believe him but would still like to see the exact question he asked.OP asked them I believe, gave a really basic answer.
Here you go, some light reading: http://hexkyz.blogspot.com/2018/06/chill-shills.html
Never trust a company that puts malicious code in their product.
Me too.I believe him but would still like to see the exact question he asked.
So you want them to have a contingency plan for something that have said countless times isn't going to happen? I understand your reasoning for wanting them to have such a plan but to do so would be to acknowledge that there is a chance that it could happen. That'd be an extremely bad PR move and undermines what they said previously.
"Guys. We're not saying this is going to happen, because it's not. But if it does, which it's not. We'll replace or send you a payload to fix your Switch".
At the best you'll get a; "Team Xecuter stands by their products and gives great technical support. If you run into any issues when running the SX OS software or SX Pro hardware then please send us an email at [email protected]".
Not trying to be a bitch but you should look at the verb:That's exactly what I want. Mariam-webster defines "guarantee" as
Definition of guarantee
1: guarantor
: guaranty 1
: an assurance for the fulfillment of a condition: such as:
a :an agreement by which one person undertakes to secure another in the possession or enjoyment of something
b : an assurance of the quality of or of the length of use to be expected from a product offered for sale often with a promise of reimbursement
So yes, if you're going to GUARANTEE that it won't happen, you need to offer something in the event that it happens. Otherwise your guarantee doesn't mean shit.
Not trying to be a bitch but you should look at the verb:
View attachment 133284
Hacking is gonna require an oxygen tank for some of yall with all this fear
That's exactly what I want. Mariam-webster defines "guarantee" as
Definition of guarantee
1: guarantor
: guaranty 1
: an assurance for the fulfillment of a condition: such as:
a :an agreement by which one person undertakes to secure another in the possession or enjoyment of something
b : an assurance of the quality of or of the length of use to be expected from a product offered for sale often with a promise of reimbursement
So yes, if you're going to GUARANTEE that it won't happen, you need to offer something in the event that it happens. Otherwise your guarantee doesn't mean shit.
The Switch too, an attempted downgrade will produce an unusable console.I guess you'll never support Nintendo as well since they had brick code back on the Wii.
And words are just words. Following through on a guarantee is what really matters and even that's not assured to you even if they were to tell you what you want to hear.
When you play around with closed source third party software this is a risk that you take. If TX says that they'll replace Switches that were bricked using their OS then that's great but just realize that there's the possibility that they won't say anything like that. If I had to guess I'd say the latter is more likely.
Are you still going to use your two SX Pros if the latter is the case?
Bans happen it's part of hacking. But all of the "What IF's" is getting ridiculous b/c at the end of the day we... don't... know. Trying to make a point based off of theories is like going through a Kingdom Hearts Fanpage.It wasn't long ago we had people reassuring everyone that no one would get banned.
Things change.
Okay so if you want to get technical, sure. But it still renders my switch useless with no way to fix it myself, even with nand backups. So what's your point?
--------------------- MERGED ---------------------------
The analogy works fine still. Just because you're not messing with SX OS, it could still accidentally trigger. Something in homebrew software could do something the SX OS sees as tampering and boom, you're bricked even though you did nothing wrong.
In the car analogy, I could hit a bump in a road. Did nothing wrong but the stereo anti-theft could think it's being tampered with. Now I'm left with a useless car.
Again, just because TX says its safe, doesn't mean anything, of course they'd say that. I just want to know what they're going to do in case something happens. I don't want to be left here with nothing but their "guarantee" just to find out after it happens that since I used some homebrew, they're not responsible. Bull fucking shit, you put this in there on purpose and now I'm out of a 300 dollar console.
Edit: And trust me, I'm not trying to hate on TX, I even pre-ordered TWO SX Pros. I just want to make sure before I use it when it comes in that I'm not just lining myself up for a door stopper.
Then dont use tx os if you feel that way, problem solvedOh trust me, I don't see them ever actually guaranteeing anything other than maybe the cost of your SX Pro dongle. So unless they remove the bricking code and someone actually verifies this, I probably WON'T be using them. More than likely selling them while the resale price is still good.
It can be fixed. You can't because you can't hack sx and this means you will never get in trouble (unless you used a cracked copy which hasn't patched out all security checks)
As stated the emmc will be locked by a "specific" password. If tx wanted they could remove the lock with a payload if it misfired.
To me it looks like they cared about possible missfire because they left this backdoor to fix it behind.
Since there was no missfire yet wouldn't it be to soon to punish them?
I don't want to defend bricking code. It shouldn't be used in the first place but as far as I can see nobody is really in danger if he doesn't try to debug the os files.
After a few thoughts your car radio analogy does fit. A stolen radio will be bricked an rendered useless for the thief without the proper key card. If it is triggered by accident the manufacturer will fix it if you can prove it is not stolen...
So they avoided the question and promoted their shit. Honestly I feel like this reply sums up why I can't stand these kinds of teams.
Oh trust me, I don't see them ever actually guaranteeing anything other than maybe the cost of your SX Pro dongle. So unless they remove the bricking code and someone actually verifies this, I probably WON'T be using them. More than likely selling them while the resale price is still good.
It can be fixed. You can't because you can't hack sx and this means you will never get in trouble (unless you used a cracked copy which hasn't patched out all security checks)
As stated the emmc will be locked by a "specific" password. If tx wanted they could remove the lock with a payload if it misfired.
To me it looks like they cared about possible missfire because they left this backdoor to fix it behind.
Since there was no missfire yet wouldn't it be to soon to punish them?
I don't want to defend bricking code. It shouldn't be used in the first place but as far as I can see nobody is really in danger if he doesn't try to debug the os files.
After a few thoughts your car radio analogy does fit. A stolen radio will be bricked an rendered useless for the thief without the proper key card. If it is triggered by accident the manufacturer will fix it if you can prove it is not stolen...
Other than the "I probably WON'T" I'm pretty impressed with your resolve towards the matter. I know a lot of people are most likely going to continue using the OS/Pro but you're sticking to your guns. Probably.
Just messing you with you.