Homebrew Install Unity exported CIA through FBI

[Apache Thunder]

Only the system app CIAs from dev use a different keyslot I believe. I think dev game CIAs are zero key too. Have you tried decrypting them with Decrypt9?

 

[Urkaz]

I don't know what Unity creates when compiling, but when building something made with the sdk you get a ".CCI" file. That file can be decrypted and then converted to a CIA with Decrypt9WIP, then you can install it wit your favorite CIA installer (I use FBI), and executed using the Luma3DS dev version with the UNITINFO option enabled.

Each time you get a new build you need to do all the steps again for the new generated CCI, it's tedious but better than nothing.

Hope this helps

 

[HaloBenish]

I don't know what Unity creates when compiling, but when building something made with the sdk you get a ".CCI" file. That file can be decrypted and then converted to a CIA with Decrypt9WIP, then you can install it wit your favorite CIA installer (I use FBI), and executed using the Luma3DS dev version with the UNITINFO option enabled.

Each time you get a new build you need to do all the steps again for the new generated CCI, it's tedious but better than nothing.

Hope this helps

I'll try this next

 

[HaloBenish]

I don't know what Unity creates when compiling, but when building something made with the sdk you get a ".CCI" file. That file can be decrypted and then converted to a CIA with Decrypt9WIP, then you can install it wit your favorite CIA installer (I use FBI), and executed using the Luma3DS dev version with the UNITINFO option enabled.

Each time you get a new build you need to do all the steps again for the new generated CCI, it's tedious but better than nothing.

Hope this helps

It installed but throws a FATAL ERROR immediately after booting in LUMA with UNITINFO. Godda get a dev kit I guess

 

[HaloBenish]

Previously farthest I had gotten with this was getting it installed but before Nintendo 3DS screen shown FATAL ERROR thrown. Now I get the Nintendo 3DS screen after booting but then thrown back to home menu then forced reboot error.

 

[Mikemk]

If you're using the dev builds of luma, try the non dev builds. And vice versa.

 

[HaloBenish]

Yea, or I'll order a dev kit on Monday and make this whole 3DS game dev thing a lot less tedious. Thanks for the help everyone

 

[Mikemk]

Yea, or I'll order a dev kit on Monday and make this whole 3DS game dev thing a lot less tedious. Thanks for the help everyone

I wish I could afford that

 

[Deleted User]

Speaking as someone who has managed to get Unity CIAs working on a retail 3DS, I can hopefully give you a brief method, that I often use, which could perhaps work out for you.

1) Download the latest 3DS Simple CIA Converter (an easy-to-use program which handles zero-key-encrypted CIAs) and place your output CCI file inside the "roms" folder.

2) Rename the CCI extension of your file to .3DS as the program only detects files with that extension.

3) Open the program and choose the option to convert 3DS to CIA. Let it do its business, and after a few seconds, the file should now be converted to a CIA, ready to be installed to your 3DS.

4) Finally, send it on over to your 3DS and install via your preferred CIA installer.

The result varies from 3DS to 3DS, most likely depending on your setup (I personally use A9LH + Luma3DS hourly) but I have always found this method of converting and trying out a Unity CIA has always 100% worked out for me!

---

I also forgot to mention that you shouldn't have ticked any of the boxes in the Build Settings (development CCI and convert to CIA image boxes), as they can also render the CIA unplayable.

 

[HaloBenish]

Speaking as someone who has managed to get Unity CIAs working on a retail 3DS, I can hopefully give you a brief method, that I often use, which could perhaps work out for you.

1) Download the latest 3DS Simple CIA Converter (an easy-to-use program which handles zero-key-encrypted CIAs) and place your output CCI file inside the "roms" folder.

2) Rename the CCI extension of your file to .3DS as the program only detects files with that extension.

3) Open the program and choose the option to convert 3DS to CIA. Let it do its business, and after a few seconds, the file should now be converted to a CIA, ready to be installed to your 3DS.

4) Finally, send it on over to your 3DS and install via your preferred CIA installer.

The result varies from 3DS to 3DS, most likely depending on your setup (I personally use A9LH + Luma3DS hourly) but I have always found this method of converting and trying out a Unity CIA has always 100% worked out for me!

---

I also forgot to mention that you shouldn't have ticked any of the boxes in the Build Settings (development CCI and convert to CIA image boxes), as they can also render the CIA unplayable.

Yee yee, must have been using the wrong program. Getting 3DS Simple CIA Converter now.

EDIT: SUPER THANKS!

 

[HaloBenish]

Anyone know where to find a GTK# windows build?

EDIT: http://www.mono-project.com/download/#download-win found it :S

 

[TuoLarips]

Speaking as someone who has managed to get Unity CIAs working on a retail 3DS, I can hopefully give you a brief method, that I often use, which could perhaps work out for you.

1) Download the latest 3DS Simple CIA Converter (an easy-to-use program which handles zero-key-encrypted CIAs) and place your output CCI file inside the "roms" folder.

2) Rename the CCI extension of your file to .3DS as the program only detects files with that extension.

3) Open the program and choose the option to convert 3DS to CIA. Let it do its business, and after a few seconds, the file should now be converted to a CIA, ready to be installed to your 3DS.

4) Finally, send it on over to your 3DS and install via your preferred CIA installer.

The result varies from 3DS to 3DS, most likely depending on your setup (I personally use A9LH + Luma3DS hourly) but I have always found this method of converting and trying out a Unity CIA has always 100% worked out for me!

---

I also forgot to mention that you shouldn't have ticked any of the boxes in the Build Settings (development CCI and convert to CIA image boxes), as they can also render the CIA unplayable.

Thank you very much for this post! You helped a lot! And I have just one thing to add here. If you have sprites that are large (2048) your game will not be playable on Nintendo 3DS.

 

[Aved]

Thank you very much for this post! You helped a lot! And I have just one thing to add here. If you have sprites that are large (2048) your game will not be playable on Nintendo 3DS.

yup, 512x512 is the max supported, learned the hard way

 

[HaloBenish]

Need to re-export [my brother's] sprites at 512X512, thanks for the help!

 

[Aved]

Need to re-export [my brother's] sprites at 512X512, thanks for the help!

can you be more specific?

 

[TariqSoftDev]

To launch a CCI un-encrypted use dev mode on your cfw

 

[haazet]

Thought I'd throw in that with Gateway you can rename the .cci to. 3ds and it runs. It really quick way to test since you don't have to convert than transfer to the 3ds, just pop out the cart. Not sure if it warrents buying one if you don't have one from a long time ago

 

[adrifcastr]

Is this possible?

Do not tick build as cia, just build the cci rename the file extension to 3ds and use the simple 3ds to cia converter, the cias made by unity are just vor Panda Dev Units

 

[N7Kopper]

Thought I'd throw in that with Gateway you can rename the .cci to. 3ds and it runs. It really quick way to test since you don't have to convert than transfer to the 3ds, just pop out the cart. Not sure if it warrents buying one if you don't have one from a long time ago

Sky3DS would be better for that, wouldn't it? No installation baggage.

 

[haazet]

Sky3ds doesn't have signatures disabled so I don't think will work. Thought I share my test project I was messing around with