4/23/2012
I am not dead! I apologize for my absence. I wanted to have enough evidence this time to make solid and more presentable data.
For the past month and a half I have been learning much more and I've been able to successfully compile CXI (CTR eXecutable Images) with accurate raw data. Last time, my CXI was (in all respects) only structurally valid; the data was not so much as valid as I was thinking. This time, however, I've been able to test the raw data and have progressed the output to be a 1:1 valid binary. I am working on proper encryption, but for this demo/progress update it now has correct structure, flags, signatures, and raw materials to be encrypted into a CXI. In other words, I've made a valid raw form of CXI for this progress update.
For those curious to see that I'm not making blind claims I'll attach a new download for a fully unencrypted (raw), but valid, homebrew CXI :
http://www.mediafire.com/?9trvb9trt32dhn7I am still working on encrypting it properly, but now I can show valid coding base progress. I've formatted this CXI to outline the CXI structure while being unencrypted. You may notice I did not include a logo binary in the ExeFS. This is because I'm not 100% sure if it is legal to distribute that (my guess is not, though) so I'd rather not post that here just to be on the safe side.
For now, with the plain region, I will use 1_2_0_200 as the version. This CXI isn't made by the official SDK (it's made through CiTRUS) so that's more of a placeholder version to ensure compatibility and match the plain region data format we see with retail CXI.
Now, with this presentation, I am showing valid structure and valid raw (unencrypted) data. I hope to soon figure out how to properly encrypt CXI to use with 3DS software.