Well sure, but after the Wii incident you would think Nintendo would have thought far enough ahead to prevent something like that haha. But I suppose you're right, we won't know until it happens. However, in my opinion, I don't think it'll be a save exploit that'll end up opening the 3DS-snip for shorter length-![]()
Of course not. I didn't say it would do a system hack. All I said was to correct your statement. The problem isn't the Save Dongle; the problem is not knowing how all of the checksums are generated yet.
Now, with neimod being able to view the RAM perhaps he can shed some light on those mysterious checksums.
Even if a save exploit isn't a system exploit, it could be used to test 3DS code before getting into the system which would run less of a chance of bricking. I don't mean Nintendo will brick the console; I mean bricking by lack of knowledge of how the system coding works and accidentally bricking the system by the user. Team Twiizers did something like that for the Wii. They started with a save exploit in Zelda to experiment with code until they were comfortable and then moved to the system. (I know, coincidentally, they also broke through the sandbox using Zelda as well)










