There is litterally no reason to wait for KTM, as long as you don't do anything dumb there are low chances of bricking.There are plenty of tutorials arround for sysupdater, should a wait for this or just simply downgrade with sysupdate?
Use a small 2 or 4 gb freshly formatted sd with only required files. format system and go. I've done 3 new3ds and 1 old with this method. The longest it took me was 5 try's. 1 new 3ds did it first time. No soft bricks either.Im not even scared of bricking, my problem with sysUpdater is that it doesnt fucking work. Been rebooting my N3DS for 3 days now
QUIT WHILE YOU'RE AHEAD. I broke my 3DS permanently on the second try.Im not even scared of bricking, my problem with sysUpdater is that it doesnt fucking work. Been rebooting my N3DS for 3 days now

Exactly, because that's the nature of the exploit, its literally a gamble (also that's how it derrek explained that works on the 32c3 talk).It is impossible to develop a downgrading tool that has no risk of hard bricking. The only way to be safe is performing a NAND backup and being able to restore it, and the only way to do that right now is with a hardmod.
There is no promises of increased stability as the issue is within the exploit itself, that is what we have gathered besides other than a "probably". There is already a lowered chance of bricking from updated sysupdaters, unless you have no idea what you're doingOkay, so what exactly is the difference between using KTM and sysupdater? like, are there any benefits to downgrading using KTM besides stability and the lowered chance of brick?


Maybe, maybe a noob-friendly SysUpdater.So this is basically an idiot-proof sysUpdater?
There is no promises of increased stability as the issue is within the exploit itself, that is what we have gathered besides other than a "probably".
