Latest revision as of 18:37, 7 May 2012

IMPORTANT[edit]

	CiTRUS
General
Author(s)	Xcution
Type	PC utility
Version	0.2
Links
	Download

The CXI generator has not been released yet, please understand it is under development. I apologize for adding in the possibility of using retail RSA keys; they would be so hard for us to get it wouldn't even be funny having them. However, when homebrew is available to this community the output should be usable, as a homebrew loader would not check the signature.

Notes from users[edit]

~~This application may not generate completely perfect files yet.~~ Banner output has been checked. It is proper data if the program is used properly. The same goes for the ICN.

General information[edit]

Introduction[edit]

Over the past weeks I have been working on Project CiTRUS (citrus). Currently this tool boasts the capability to output proper Nintendo 3DS (CTR) BaNneR and ICoN files using my XBSF format.

You may notice that creating these formats is not yet available in any other released tool. Over the course of time I will do my best to add creating new formats of 3DS files among various other calculations if I see users are liking the program.

If you have v0.1 please update it! There are new bug fixes, GUI changes, and updates! It is also more n00b compliant than the previous version. (now has a lot of help text)

I do not include an editor for the image formats, however, I do include an example of each required file for generating a test banner/icon. I do this not to troll, but rather in the hopes that it will encourage other talented users to make programs for the 3DS.

USE[edit]

Since v0.2, a readme is not really necessary anymore. I've included helpful text inside each tab in the CiTRUS window to do things on-the-fly without needing to switch between notepad (or your favourite text editor) and CiTRUS.

INPUT:

1x XBSF (Xtended Banner Specifications(Spec) File)
2x CTPK (CTR Texture PacKage)
1x BCWAV (Banner CTR Wave)
1x CBMD (CTR Banner Model Data)

OUTPUT:

1x BNR (Optional)
1x ICN (Optional)

ISSUES[edit]

I don't think there is any, but since this is a beta please report to me if there are issues that come about!

UPCOMING[edit]

5/7/2012

Well, it's been a fun 7 months so far.

Encrypted, proper CXI:

http://www.mediafire.com/?hcm1p6fq4x7q14o

Signatures, Hashes, ExeFS, Extended Header, Flags[-], NCCH header, and encryption are now valid. The only thing left now is the RomFS.

[-] = It seems flags for developer applications may differ from retail application flags, but it is not a big deal as when retail applications can be decrypted I can replace and change my flags to fit retail needs. The generated CXIs would still require an exploit to run on a retail 3DS, however. The flags are already laid out and are valid developer flags, though.

UPDATES[edit]

Version 0.2:

Fix: "Polish" changed "Portuguese"
Fix: Can now Set region to Taiwan
Fix: Can now Set rating to true

Add: Colour scheme of menu items to match colour scheme menu bar
Add: ComboBox for regions and ratings
Add: Checkboxes instead of true/false typing
Add: Automatic saving before building
Add: Banner writing progress bar/notification of finishing
Add: Help box incorporated into each tab (except title name/publisher tabs because those are not so complicated)
Add: Name now reflects what's on here (CiTRUS) and version number (v0.2)

MEDIA[edit]

@@ Line 57: / Line 57: @@
 ==UPCOMING==
-/23/2012
+/7/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.
+Well, it's been a fun 7 months so far.
-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.
+Encrypted, proper CXI:
-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/?hcm1p6fq4x7q14o
-http://www.mediafire.com/?9trvb9trt32dhn7
+Signatures, Hashes, ExeFS, Extended Header, Flags[-], NCCH header, and encryption are now valid. The only thing left now is the RomFS.
-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.
-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.
+[-] = It seems flags for developer applications may differ from retail application flags, but it is not a big deal as when retail applications can be decrypted I can replace and change my flags to fit retail needs. The generated CXIs would still require an exploit to run on a retail 3DS, however.
+The flags are already laid out and are valid developer flags, though.
 ==UPDATES==

Difference between revisions of "CiTRUS"