I made aeskeydb.bin and (with the other keys removed) the self tests all passed. The only .3DS I had to decrypt was Ghost Recon: Shadow Wars which is old so maybe didn't even use the keys(?), but it worked regardless.
My System Info looks correct. Recognises N3DS, NAND size, region, A9LH, GW emuNAND. At first I thought it was a mistake that under keys set 0x18X was listed when I only had the other three on my SD, but after holding L+R on startup I saw that that one is apparently already set up.
I did notice one weird thing with the L+R info. Normally without keys present it reports this:
Code:
Initializing SD card... success
0x03 KeyX & KeyY: automatically set up
0x05 KeyY: not found
0x25 KeyX: not found
0x18 KeyX: already set up
0x1B KeyX: not found
Finalizing Initialization...
Initialization: failed!
However, if with the keys already loaded (either individuallly or in aeskeydb.bin) I unmount my SD, delete the keys, reinsert SD, (remount or don't), reboot and go straight back into D9 (via AuReiNand chainloader and CTRBootManager9) it reports that 0x25X is also already set up:
Code:
Initializing SD card... success
0x03 KeyX & KeyY: automatically set up
0x05 KeyY: not found
0x25 KeyX: already set up
0x18 KeyX: already set up
0x1B KeyX: not found
Finalizing Initialization...
Initialization: failed!
Seems weird but probably not important? Powering off makes it go back to normal next time.
My 2.1 NAND backup validated successfully. I made it a few weeks ago before OTPHelper had all its validation features added, so the only corroboration I have of it being good is that I got my OTP ok