If Nintendo manages to patch the SX OS with future updates, you can just wait for them to update the payload and bypass the patch. That's exactly how GW did it for years with the 3DS. Nintendo can't patch this.
I have only heard the pins being damaged either due to paperclips (physically) or tin foil (electrically). The plastic jig model itself is made to be the right size that fits perfectly into the Switch rail. However, the metal wiring is a variable that depends on the skill of whoever is making the jig.One could simply not install autoRCM, right? But if I've been hearing correctly, the pin connectors also have a chance to break a pin each time they're inserted, correct? Or if you have them at the right length/size are they safer?
Yes, dude, no worries - you will be able to, until at least the next Nintendo firmware update!
When they patch out and obfuscate the entrypoints for the hooks TX' uses to get their piracy loader running. At which point you'll have a TX' solution, that has your switch only turning on via a dongle - and then no CFW functionality on top of that. No worries - its gonna be great.
Just please promise, that you dont come to this forum for support then. Thank you.
Here is a quick firmware update tip for Nintendo.
Push out an update in the next few days, that will prevent users from using L and R in the launcher interface. It will be hilarious.
A better post would be why you have taken stance, i'm not saying it's wright or wrong, just interested why.Also I really hate the concept of people buying DRMed CFW. (Full disclosure.)
I see. Makes sense.The access points (where i assume TX hijacks the requests, and redirect where they need it to) will still have to be there, or the OS / Switch wouldn't be able to use it.
So a simple patch updating the memory address would be almost trivial.
Adding an Encrypting and Decrypting routine on every read request to a cartridge / install location would have an interesting hit on performance, especially on a console with limited hardware to begin with (on top of the late implication of this feature).
I've already acknowledged that, but the bigger point is, that once Nintendo gets their hands on the TX'os - they can write out its hooks and turn it in circles. Also - changing button combos - every time, would confuse the TX userbase...Then TX can update and change the hijack to LB + up (for example), or just patch the OS to allow it again.
There are other things at play - like "never mess with a gui" ("integrity of look and feel" ) that might stand against that specific thing as well.
But people really wanted to know, if nintendo could patch this going forward - and the correct answer always is, yes - absolutely.
Everyone looking at their concept, sees - that the "compatible with every firmware" slogan will hold up unitil one month after launch max - at which point it will become a back and forth (to randomize memory spaces, write out access points, put processes on blacklists, or in containers... the usual)
This i disagree with.Can TX update there CFW, to beat most (never say all) changes Nintendo make, most probably.
Yes, and then no online, no new games, and people in a weird state of limbo - with a Switch with maybe "too many efuses burned for the firmware its on" - which gets supported by whom? Xecuter? (Still dependent on official firmware releases.)TX can freely downgrade peoples OFW as long as the fuses dont get set. And if nintendo did this while burning fuses, It wouldn't take long to deplete them.
Man you don't have the slightest idea of how this whole thing works, rcm, cfw, tx, switch os, nothing, why are you even losing time typing this bs? Go on reddit ffs or come back after you've learned something.Yes, and then no online, no new games, and people in a weird state of limbo - with a Switch with maybe "too many efuses burned for the firmware its on" - which gets supported by whom? Xecuter? (Still dependent on official firmware releases.)
Online is gone. Chance for a softmod only in the future is all but gone, new games are gone, system integrity (nand, efuses) is gone - but TX sold product to people that couldnt wait. Thats the deal, right?
TX' should make a vow right now to always support their customers with concerns like this for the next two years. Because people like me as sure as heck wont (on forums like this one.. ).
Limited piracy for people that want to get banned and stuck on 5.0.2 for the rest of their lives. (Or for how long TX takes to reverse that next firmware - and then the next. And the next.)
In terms of "number of efuses that can get burned" - what is it?
Because if you say N cares about the Switches performance for another 3 years (until used game prices get low enought that piracy is less appealing), thats 36 months - how many efuses do they have left?
You could just put him on ignore.@notimp Stop trolling TX threads. You've made it abundantly clear you have a shockingly low comprehension of how CFW even works and you are going around lecturing people about things you know almost nothing about. It's a little embarrassing for you, but mostly mind-numbingly annoying for us.
Yeah but you know, I think that pokemon will be bought by basically more than a half of the switch users, and that will be a great time for big N to purge an important update that may block something regarding the hack scene.I won't quote notimp because it's too big, but what you're talking about is pointless, a new update every month cat and mousing? People will still be able to play every game, look how long it's taken for a cart to land that has 5.0+ on it. By the time you see a cart with the latest OFW that FW has been in the hands of TX for months
When they patch out and obfuscate the entrypoints for the hooks TX' uses to get their piracy loader running. At which point you'll have a TX' solution, that has your switch only turning on via a dongle - and then no CFW functionality on top of that. No worries - its gonna be great.
TX "works on all firmwares" is a nice slogan - for about six weeks.