It doesn't install for me, how do I sign development CIAs so they can be installed through fbi?
Dev CIAs are encrypted using an unknown keyset which differs from normal keys. Unity will also have created a *.cci file. That's a gamecard image (same as *.3ds), and uses the normal keyset. You can either rename it *.3dz and use in gateway, or convert it to a cia using tools found elsewhere on the temp.
both...Have you tried the .cia? Or only the converted CCI?
Try it with an empty project.both...
Only converted cci is installing but it crashes on boot
Try it with an empty project.
Also, how did you get the 3DS build option to activate? I have the official thing from Nintendo, but it doesn't have a 3DS or Wii U option
The first thing I said about the unknown keyset was said by someone else on the temp. The second thing was a question, so NDA doesn't apply to me. (It would to the answerer though, but if they downloaded from a leak instead of NDA, they can answer)[Caution!!] When talking about anything related to the Nintendo Developer Program that you have learned/acquired by being a part of it.
I believe the keys are actually known, but I have no idea how you'd decrypt it to make it work on retail 3DSes.Dev CIAs are encrypted using an unknown keyset which differs from normal keys. Unity will also have created a *.cci file. That's a gamecard image (same as *.3ds), and uses the normal keyset. You can either rename it *.3dz and use in gateway, or convert it to a cia using tools found elsewhere on the temp.
How did you get it to run?The first thing I said about the unknown keyset was said by someone else on the temp. The second thing was a question, so NDA doesn't apply to me. (It would to the answerer though, but if they downloaded from a leak instead of NDA, they can answer)
In the meantime, I figured it out.
Read the instructions on Nintendo's website carefully, and make a note of the product keys.How did you get it to run?