-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SeedDB limit? #171
Comments
Can you try this in GodMode9? Just select the ncchinfo.bin file and let it generate the XORpads. |
Alright... this should work in GodMode9. Increasing the allowed db size in Decrypt9WIP is more complicated, so you either need to use a smaller seeddb.bin or you have to switch to GM9. |
Well GodMode9 requires user to be professional in 3DS otherwise users may lost their way to find what the necessary file is required for the function they want. |
This is not a platform for discussion, so here's my 5 cents... I'm not hindering people from staying with Decrypt9WIP & Hourglass9, however I'm encouraging the use of GM9, simply because it's superior software (and that also includes a superior interface). You need to be "professional in 3DS" to use GodMode9? I don't think so. Creating NCCH xorpads.... ... in Decrypt9WIP ... in GodMode9 How the latter requires you to be professional, I don't know. Decryption and CIA build stuff is equally as easy. aeskeydb.bin is no more required if GM9 is ran via sighax. There is also a small section called "Quickstart Guide" in the GM9 readme that you can follow (if you want). The readme for D9 is equally as large as the GM9 one and describes all the possibilites. The thing that makes D9 easier is that you have all the things it can do at a glance. But... you know what you want to do, right? Anyways, tl;dr, don't be afraid of GM9. Only leaving this open because someone else may want to fix it later. |
Well..... |
my SeedDB.bin has 1110 seeds and Decrypt9WIP throws an error
"Selected: [NCCH Padgen]
Opening seeddb.bin...
Bad number of seeddb entries
NCCH Padgen: failed!
Press B to return, START to reboot."
The text was updated successfully, but these errors were encountered: