No edit summary |
No edit summary |
||
| Line 18: | Line 18: | ||
CRO/CRRs modified with this tool will only work on 3DSes with PS:VerifyRsaSha256 patched in some form. On pirate CFWs, this is patched already. ARM11-based hacks which allow for romfs-file replacement won't work with this (though none exist/are out yet). | CRO/CRRs modified with this tool will only work on 3DSes with PS:VerifyRsaSha256 patched in some form. On pirate CFWs, this is patched already. ARM11-based hacks which allow for romfs-file replacement won't work with this (though none exist/are out yet). | ||
==Usage:== | |||
*cro_tool [-v] static.crr | *cro_tool [-v] static.crr | ||
*-v: verify crr/cros instead of rehashing/resigning | *-v: verify crr/cros instead of rehashing/resigning | ||
Revision as of 14:24, 23 September 2021
Template:Infobox-3DS-Homebrews
It came to my attention recently (@SciresM mentioned it elsewhere) that even with RSA checks patched, hacked 3DS app libraries (CROs) still won't run when patched. Because of that, I threw together this tool to allow exactly that.
Hopefully this will help ROM hackers who've wanted to modify their games, but have been held back due to this. Pokemon, I've heard, has an assload of the game 'locked up' in CROs.
CRO/CRRs modified with this tool will only work on 3DSes with PS:VerifyRsaSha256 patched in some form. On pirate CFWs, this is patched already. ARM11-based hacks which allow for romfs-file replacement won't work with this (though none exist/are out yet).
Usage:
- cro_tool [-v] static.crr
- -v: verify crr/cros instead of rehashing/resigning
Make sure you've got all the app's CROs in the same directory as cro_tool. Afterward you can even just drag-n-drop static.crr onto cro_tool (you should probably run it from cmd/shell to make sure it's working, though.)