Until you have a quantum computer.too many combnations tho it will take you more then a life time to crack it
Until you have a quantum computer.too many combnations tho it will take you more then a life time to crack it

Then that's almost useless currently. Even the loaded address is known, and your own code could be done..arm9loader loads FIRM from NAND. But arm9loader is decrypted and loaded by the bootloader. And the keyslot is cleared, because the payload is executed after arm9loader. So you can't regenerate the decryption keys. And the problem, is that you have to bruteforce to have something bootable and that does "what you want".
Yup, but I don't think anyone would care to do that, when we have downgrade and menuhax. Plus, it would have to be done for each N3DS.Then that's almost useless currently. Even the loaded address is known, and your own code could be done..
Bruteforcing the decryption to have a Jump Command is surely a job with unknown trails, even that must be easier than bruteforce Math.pow(2,128).
-- Cause what you need is only a valid BL after the FIRM0 section in ram, you don't need to place it exactly after the FIRM0.
Whatever, good luck to devs.
33%, see me after class..CXI = .3DS files

can you not ask about it and other unrelated things in this threadcan they be converted into cia
Thanks. I was too lazy to explain.33%, see me after class.
CXI == CTR eXecutable Image. A CXI is a specialization of the NCCH format and contains at least an ExeFS, and optionally a RomFS. A CCI (CTR Cartridge Image == .3DS) contains at least one CXI, which is the main content of the CCI; however, a CCI can contain more CXIs in theory. In practice, slot 0 of the CCI is always the main contents and the other slots are only used for CFAs (CTR File Archives), such as update data (which is a collection of CIAs of system titles) and the manual.
See also: http://3dbrew.org/wiki/NCCH#CXI and http://3dbrew.org/wiki/NCSD#Overview

Oh no. .3DS is NCSD type, a NCCH container type, CIA is also a container type..CXI = .3DS files
And braindump 1.0 allows you to dump them. But they are not signed.
I've also noticed that CCIs == CSUs too, which can be then converted into CIAs through a certain converter which isn't available anymore.33%, see me after class.
CXI == CTR eXecutable Image. A CXI is a specialization of the NCCH format and contains at least an ExeFS, and optionally a RomFS. A CCI (CTR Cartridge Image == .3DS) contains at least one CXI, which is the main content of the CCI; however, a CCI can contain more CXIs in theory. In practice, slot 0 of the CCI is always the main contents and the other slots are only used for CFAs (CTR File Archives), such as update data (which is a collection of CIAs of system titles) and the manual.
See also: http://3dbrew.org/wiki/NCCH#CXI and http://3dbrew.org/wiki/NCSD#Overview

These types are all NCSD, so they have a similar structure.I've also noticed that CCIs == CSUs too, which can be then converted into CIAs through a certain converter which isn't available anymore.
No, those dev CSUs can be converted to CIAs for retail units. I managed to do that for all of the SDK Devkit tools.These types are all NCSD, so they have a similar structure.
However CSU is used by ninty for its dev units to Update the System, thus there is U in it. (CTR System Update)
Also to note there is no .CSU for Retail console. CCI is for games, correspondingly.
Hope there is something hidden and amusing.

I know that, and i can do that too. NCSD can be converted to CIA, and you can also make a CXI to be wrapped to a CIA, with some info provided.No, those dev CSUs can be converted to CIAs for retail units. I managed to do that for all of the SDK Devkit tools.
I didn't intend to get into details about this stuff.I know that, and i can do that too. NCSD can be converted to CIA, and you can also make a CXI to be wrapped to a CIA, with some info provided.
However that does not prove something more. I still can not decrypt the CSUs from Ryan on twitter. The files seems encrypted using another key.

Okey. I just know the Dev Unit System Update is in CSU, and no corresponding CIA ever heard of.I didn't intend to get into details about this stuff.
I don't even know what NCSD is lol.Okey. I just know the Dev Unit System Update is in CSU, and no corresponding CIA ever heard of.
Yes, for most guys you can simply think the two types are the same one. They are all NCSD.
http://3dbrew.org/wiki/NCSDI don't even know what NCSD is lol.![]()

Yes this is true, it would need hardmod, trails, and console different (cause the NAND). Even a system update to FIRM would cause another try, quite boring for some.Yup, but I don't think anyone would care to do that, when we have downgrade and menuhax. Plus, it would have to be done for each N3DS.