Line 8: |
Line 8: |
| }} | | }} |
| | | |
− | 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. | + | = '''IMPORTANT''' = |
| + | 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 = |
| + | <del>This application may not generate completely perfect files yet.</del> |
| + | Banner output has been checked. It is proper data if the program is used properly. The same goes for the ICN. |
| + | |
| + | = General information = |
| + | == Introduction == |
| + | 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. |
| | | |
| | | |
Line 25: |
Line 34: |
| | | |
| ---- | | ---- |
− |
| |
| | | |
| == USE == | | == USE == |
| | | |
− | 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 and CiTRUS. | + | 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: | | INPUT: |
Line 49: |
Line 57: |
| ==UPCOMING== | | ==UPCOMING== |
| | | |
− | Currently I am working on some *ahem* things I would like to keep private until they are stable as I am currently unsure of how long it will take or even if they will eventually be stable.
| + | 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. |
| + | |
| | | |
− | Please stay tuned!
| + | [-] = 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== | | ==UPDATES== |