Can you give more details? What's stuck on the loading screen? Is GodMode9 unable to load or is it stuck when you choose to install FIRM to firm0?
Stuck on the loading screen while you startup GodMode9, I have long deleted that though and have tried redoing a bunch of things.
@AnalogMan
https://imgur.com/a/DoWiX
It's likely because it can't obtain the system keys, which it would normally get from your already existing b9s install, which you don't have. While I can't link you the keys directly, if you read the GodMode9 release page, you can find a file called aeskeydb.bin by googling the MD5 hash of A5B28945A7C051D7A0CD18AF0E580D1B
If you manage to find it on your own (it'll be 1024B big) copy it to your SD:/gm9/support/ folder on the SD card and see if GodMode9 will load then.
Last edited by DocKlokMan,
So you're saying you had aeskeydb.bin in the SD:/gm9/support/ folder and GodMode9 still got stuck on the loading screen?
My aeskeydb.bin is completely fine... Checked the MD5 and it's 1024 KB but My seeddb.bin and encTitleKeys.bin though... idk. Anyone have the exact MD5 for that?
SD/gm9/support:
https://imgur.com/a/Ij7S7
aeskeydb.bin MD5:
A5B28945A7C051D7A0CD18AF0E580D1B; 1,024 bytes
seeddb.bin MD5:
8636EFD9DA90D90CD467AEA0EBCA2605; 21,232 bytes
encTitleKeys.bin MD5:
178DE6B622059A0B4511BB89C5B0550D; 155,728 bytes
SD/gm9/support:
https://imgur.com/a/Ij7S7
aeskeydb.bin MD5:
A5B28945A7C051D7A0CD18AF0E580D1B; 1,024 bytes
seeddb.bin MD5:
8636EFD9DA90D90CD467AEA0EBCA2605; 21,232 bytes
encTitleKeys.bin MD5:
178DE6B622059A0B4511BB89C5B0550D; 155,728 bytes
No such thing as an exact MD5 for those. seeddb and *titleKeys depend on which titles you have installed, or which ones were present at the time you downloaded those files (and probably also depends on the order in which software was added). The only time you'll get a matching md5 from those is if you AND someone else downloads them from the same place at roughly the same time. At any rate, it probably has nothing at all to do with your current issue.
Last edited by urherenow,
Oh so how would I be able to put those files in /gm9/support? Is there a specific one I need?
Maybe... provided that your other things are setup correctly. I'll do a quick rundown because I tend to get confused reading through several different people trying to be "helpful"
1) For setting up your NTRBoot Flashcart, you should have /ntrboot/boot9strap_ntr.firm and the .sha
^^This is only for flashing your ak2i or r4 (not needed if done with .nds instead of a hacked 3ds)
2) For installing/upgrading b9s, you need /boot9strap/boot9strap.firm and .sha
^^Nothing from an NTRBoot looks here, so you will NEVER use boot9strap_ntr.firm here... that is only needed for the NTRBoot card itself. Only Safeb9sInstaller will look in this folder.
3) of course when installing b9s, boot.firm should be safeb9sinstaller (unless you flashed a modified boot9strap_ntr.firm to your card that happens to look for ntrboot.firm or ntr_boot.firm)
If you did everything with the correct files in the correct spot, nothing should prevent your system from working (once you replace boot.firm with luma or something), or godmode9 from working either. At that point, you either have an SD card problem, or a physically damaged nand (unlikely). If sd tools don't show issues with your SD then I would suggest checking every detail of your formatting (cluster size, as well as making sure it's fat32)
EDIT: Have you tried a different SD card? There is a third, unpleasant cause, which would be a failing SD card socket...
Last edited by urherenow,
Hm... I do have a second SD card I could try... again. As for the third one I doubt it, along with the NAND, I think its the SD card. I'm going to format both cards, then use guiformat instead of windows format to correct the 32 kb clustersize if thats the issue.
Similar threads
- No one is chatting at the moment.
