This is something that has been bothering me for a little while now, the "brilliant" tempers have decided that sigpatched sysNAND is a great idea. Smart right, *rolls eyes*. This is by far the worst idea i've heard in a pretty long time, since you're basically opening the paths to bricks. Since apparently everyone's too lazy to setup redNAND, they've decided that they should go the easy route and use sigpatched sysNAND, I'm gonna assume most of you know a little bit about 3ds hacking, so i'll explain it in that way, you know PastaCFW? The one that allows you to use sigpatches on sysNAND, which isn't the best idea. So i'm gonna say that it's not the best idea to use a sigpatched sysNAND and i'll state some reasons why, first of all, bricks are easy.
You could say that if you only want to install games then you're fine, which is true, but if you're just installing games you don't need sigpatches at all, so don't use sigpatched sysNAND, you're just giving yourself a chance to brick. So there's really no point of using it whatsoever, second of all is the obvious brick chance, if you install anything wrong you'll brick, point closed. Now there's the point of convenience which seems to be the only reason people are using this since everyone's lazy, IT'S USELESS. OKAY?! You can't install anything like a bad system title or sysConfig tool on sysNAND because it'll either brick or just not work on reboot. If you use redNAND you actually can use stuff. I'm not even going to go into the stupidity that is the risk of bricking with this, along with the fact that it's literally useless...
I'm really tired of people saying "Oh, we need to wait for salts stable tools, because this isn't stable and WE'RE ALL GONNA DIE!!!! OMG!!! WAIT FOR SALTS, it's not gonna be any more stable then this. We already have a perfectly stable redNAND.
Oh, and you'll never be able to use the coldboothax solution that smea's made up with sysNAND, it'll have to be redNAND; so please, install redNAND and stop risking your console for minor convenience. In conclusion, it's not worth the risk. And you should know that; thank you for reading my thread, I hope you switch from sysNAND to redNAND.
You could say that if you only want to install games then you're fine, which is true, but if you're just installing games you don't need sigpatches at all, so don't use sigpatched sysNAND, you're just giving yourself a chance to brick. So there's really no point of using it whatsoever, second of all is the obvious brick chance, if you install anything wrong you'll brick, point closed. Now there's the point of convenience which seems to be the only reason people are using this since everyone's lazy, IT'S USELESS. OKAY?! You can't install anything like a bad system title or sysConfig tool on sysNAND because it'll either brick or just not work on reboot. If you use redNAND you actually can use stuff. I'm not even going to go into the stupidity that is the risk of bricking with this, along with the fact that it's literally useless...
I'm really tired of people saying "Oh, we need to wait for salts stable tools, because this isn't stable and WE'RE ALL GONNA DIE!!!! OMG!!! WAIT FOR SALTS, it's not gonna be any more stable then this. We already have a perfectly stable redNAND.
Oh, and you'll never be able to use the coldboothax solution that smea's made up with sysNAND, it'll have to be redNAND; so please, install redNAND and stop risking your console for minor convenience. In conclusion, it's not worth the risk. And you should know that; thank you for reading my thread, I hope you switch from sysNAND to redNAND.
Last edited by iAqua,
like a 250 dollar kit back when DDR4 was Intel only