I'd love to pick a switchme, but EvilSperm (the dude selling them) told me he doesn't sell single units anymore. Not sure where to look for now.Best permanent solution that will never be patched is a modchip. Pick up a SwitchMe for like $10.
There are re-sellers posted on the website, see if you can find one close to you.I'd love to pick a switchme, but EvilSperm (the dude selling them) told me he doesn't sell single units anymore. Not sure where to look for now.

Because SciresM was the one who stated that there's a theoretical coldboot exploit up to 3.0.1 (his exact words were <3.0.2) likely due to a change implemented in firmware 3.0.2. But you're right in that since they share the same number of fuses, one could just downgrade from 3.0.2 to 3.0.1 as long as their fuse count is 4.Why are people saying "up to 3.0.1"?
Isn't it actually 3.0.2?
If someone is on 3.0.2, can't they technically downgrade to 3.0.1 since 3.0.1 -> 3.0.2 burns no fuses?
OP, if you want a permanent solution, just find someone with soldering skills and get them to install a trinket or this thing for you...Hi Guys!
I'd really appreciate some informative answers on this matter especially from @CTCaer, @rajkosto or @Reisyukaku (who quite know best how payloads work).
I understand that a few months back although the possibility to write in the Switch NAND was there it was avoided as there was no way to restore a corrupt NAND.
Now with the achievements done in the scene (NAND backup & restore, ChoixduJour), is it possible to modify some of the system files (like AutoRCM does) to have a permanently patched CFW?
The intention for this is to be able to normally boot into the CFW without using a payload (obviously) and do away with AutoRCM.
Got it. Thanks for the info.Because SciresM was the one who stated that there's a theoretical coldboot exploit up to 3.0.1 (his exact words were <3.0.2) likely due to a change implemented in firmware 3.0.2. But you're right in that since they share the same number of fuses, one could just downgrade from 3.0.2 to 3.0.1 as long as their fuse count is 4.
In layman’s terms Permanent cfw means exactly that, permanent! You don’t have to go through any loop holes to boot your cfw up so for example cbhc you do because you need the DS title on the wiius memory to be exploited to run the cfw so that’s not permanent.It's a soft mod that doesn't require you to use any button input or dongles or whatsoever when you power it on. So I don't see a reason why it's not a permanent cfw.
Trust me it’s not classed as a “permanent cfw” I’m not going to explain
I edited that part out I have explained above and that will do. cfw is one thing the exploit it uses is completely different we need an exploit to boot the cfw. We have had a few permanent cfw in the past Xbox360, Wii, PSP, 3ds, psvita that’s just of the top of my head!What's not permanent about it? By your definition, there has never been a permanent cfw. All cfws rely on "loop holes to boot."

Well guess what. The 3DS's CFW also relies on an exploit on boot up. B9S uses a signature hack in Nintendo's crappy RSA implementation in order to boot unsigned code.I edited that part out I have explained above and that will do. cfw is one thing the exploit it uses is completely different we need an exploit to boot the cfw. We have had a few permanent cfw in the past Xbox360, Wii, PSP, 3ds, psvita that’s just of the top of my head!
We can't modify anything. AutoRCM only works because it exploits a flaw in the RCM mode that gives us full access, we have no public exploit in the early boot process of Horizon that would allow us to do the same thing. Even AutoRCM doesn't allow us to modify the system, only patch memory/files on the fly. But anything could happen in the future.Hi Guys!
I'd really appreciate some informative answers on this matter especially from @CTCaer, @rajkosto or @Reisyukaku (who quite know best how payloads work).
I understand that a few months back although the possibility to write in the Switch NAND was there it was avoided as there was no way to restore a corrupt NAND.
Now with the achievements done in the scene (NAND backup & restore, ChoixduJour), is it possible to modify some of the system files (like AutoRCM does) to have a permanently patched CFW?
The intention for this is to be able to normally boot into the CFW without using a payload (obviously) and do away with AutoRCM.