Looks like some stuff about a9lh is more complicated than I though. Normally, if you can mount the partition and the file system shows up, everything should be fine (with reading at least) , but apparently there is still a problem. Will need to find out...
This in Decrypt9 is the same problem. I guess I'll need to check if the ctr calculation really works 100% and if the keys really are set. It should work from other entry points though.
There is something that you can try for us to find out what is exactly that does not work on A9LH (on some systems?). It would involve dumping a very small file from (1) a9lh and (2) another entrypoint and comparing the output. I still have to put it together, though. Later...
yea, it's sdcard only.
I think the only thing that's modified on it is the patched agb firm from when my nands were linked before I screwed something up after downgrading.
Thank you! I installed it, but it required the TWL patch. After hours for finding the right CFW, I finally was able to load it through RxTools 3 beta. Now. if this application did the same, too.
I have a N3DS, that problem is on A9LH... :/
Oh well, all those new possibilities.... With AuReiNAND you also need the firm90.bin (or something like that, as far as I know). The .dat is for CakeHax, you can also take a look at the Decrypt9 readme.
I'm currently working on a self test feature in Decrypt9... that will, in short, test everything relevant in one go. No need to test each feature. Then we will see how bad the situation really is. I somewhat fear we will need some half-CFW later to be able to properly run Decrypt9 again.Well, yeah, should have mentioned it.... (you should really install a9lh so you can keep up with us
As in? I have A9LH, same screen init version on both of my N3DS and O3DS XL systems and the feature indeed works on O3DS XL but not on N3DS, nor for some others with N3DS either.
Maybe A9LH is also just too 'young' now, and better compatibility will come later. Dunno yet... Let's assign the situation with that self test, then proceed from there. It is also possible that on these N3DS consoles, the AES keyslot is not properly set.
Sure, you're the boss man now and forever for sure. I am no authority in code, crypto and making delicious sandwiches. I leave you, d0k3, the master of delicious sandwiches to ascertain what is needed the most in the codes'n'stuff department.
I'm getting the same issue. here's a log:
Opening /D9Game ...
Processing CIA "Super Mario World (000400000F700E00).cia"
Pass #1: CIA decryption...
Decrypting Content 1 of 2 (3MB)...
Verifying decrypted content...
Verified OK!
Decrypting Content 2 of 2 (1MB)...
Verifying decrypted content...
Verified OK!
Pass #2: NCCH decryption...
Processing Content 1 of 2 (3MB)...
Code / Crypto: KTR-N-UAAE / Secure4 Seed
Warning: Secure4 support is preliminary!
Decrypt ExHdr/ExeFS/RomFS (2kB/1311kB/2MB)
Verify ExHdr/ExeFS/RomFS: OK/Fail/Fail
Failed!
Processing Content 2 of 2 (1MB)...
Code / Crypto: CTR-P-CTAP / Seed
Decrypt ExHdr/ExeFS/RomFS (0kB/0kB/1MB)
Verify ExHdr/ExeFS/RomFS: -/-/OK
Recalculating hash...
Recalculating TMD hashes...
Failed!
CIA Decryptor (deep): failed!Secure4 is supported, but untested (had no test objects so far). You need the slot0x11key96.bin, which you seem to have. Do you have the correct one and can you make sure? I have no way of testing it now.The new SNES VC games use secure4.
