Your .code is fine?! We need this, pronto!My exefs .code and exheader is fine (banner is corrupt but who cares). Romfs has a problem in level 3.
For those wondering how to tell what parts are fine or broken, you just use the following command on a decrypted .cxi:
ctrtool -i -y ctraging.cxi > info.txt
And then Cntr-F FAIL to see which parts are broken. Signatures can be broken, that's no big deal. The sha256 hashes are the important ones.
Another thing the OP left out is extracting the correct size of ctraging from your ctr-nand. You take the u32 (4 bytes) right after the 'NCCH' and multiply X 0x200. Don't forget that size is in little endian (reverse byte order) and to start from the beginning of the "NCCH" - 0x100.
What we need is a way to piece a working copy together. Don't know how we'd organize such a project though.