Yeah, I made an emunand of my 6.0 post-hack, then restored my pre-hack 6.0 nand dump, then updated. Definitely liking the SX-OS 2.3 update.
yes, they are waiting for SciresM to release an update for Atmosphere so they can steal the fix
yes, they are waiting for SciresM to release an update for Atmosphere so they can steal the fix
Weren't we told way back that the hardware exploit could "never ever" be patched out? Yet here we are?
a little inconsistent are you. "it sucks...I only use it because of this really cool feature..." roflWell, that's ok- OH NO, PLEASE NOT THE SX VERSION WITH AUTO GAME CARD EJECTING, IT SUCKS
--------------------- MERGED ---------------------------
well, SX sucks, not just that, I only use it because of HDD XCI support
It’s nothing to really worry about it’s just a new keygen I’d give tx a week or two. The others maybe a bit longerWeren't we told way back that the hardware exploit could "never ever" be patched out? Yet here we are?
It’s nothing to really worry about it’s just a new keygen I’d give tx a week or two. The others maybe a bit longer, I remember the 3ds did something similar when the Pokemon games came out
although TX just spit some big game with the new Beta announcement...seems like the new "unhackable" is not unhackable!!
[QUOTE="SageIsSerious, post: 8388318, member: 469761]although TX just spit some big game with the new Beta announcement...seems like the new "unhackable" is not unhackable!!
Even the non-hackers should, since Nintendo changing a bunch of stuff could inadvertently (or quite intentionally) break a lot of homebrew.
I don't plan on hacking my Switch, at least, not for a very long time.
Everything leading up a CFW doesn't have to be a single exploit. The hardware flaw will *always* be there, but there's more to it than that. You could nuke your NAND, and you'd still be able to run code through RCM.