Changes

265 bytes added ,  03:05, 24 April 2012
no edit summary
Line 72: Line 72:     
I 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.
 
I 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.
     
157

edits