Hacking [Release] PlaiCDN: Download and create installable CIAs (or .3ds) with just a title ID and titlekey

[Fennik]

That didnt change anything, uninstalled the the app but nothing changed. Thought that since brew was installing python3 that it was also installing another python.framework so i deleted the whole framework that the plaicdn error was linking to, found out i was wrong since pip3 didn't work after reinstalling python3 with brew.

Played around with it now get a slightly different error

Building 0004000e00119a00.cia...
Traceback (most recent call last):
  File "plaicdn.py", line 546, in <module>
    call(dotcia_command_array, stderr=STDOUT)
  File "/usr/local/Cellar/python3/3.5.1/Frameworks/Python.framework/Versions/3.5/lib/python3.5/subprocess.py", line 560, in call
    with Popen(*popenargs, **kwargs) as p:
  File "/usr/local/Cellar/python3/3.5.1/Frameworks/Python.framework/Versions/3.5/lib/python3.5/subprocess.py", line 950, in __init__
    restore_signals, start_new_session)
  File "/usr/local/Cellar/python3/3.5.1/Frameworks/Python.framework/Versions/3.5/lib/python3.5/subprocess.py", line 1544, in _execute_child
    raise child_exception_type(errno_num, err_msg)
PermissionError: [Errno 13] Permission denied

 

[cearp]

ooh yeah i just realized when i looked at the code on gitbhub... the cias this makes will not be good...
because the contents are decrypted in order to make the cia.
so, if you then want to get the same thing from the eshop, you will have problems because you will have a dirty ticket.
i think you will get that 99% error, because the stuff you download from eshop will be trying to be decrypted with the incorrect key.
if you guys really want to use keys and not share full tickets... then why aren't you sharing the encrypted key and using this to build the cia?
let the 3ds do the decryption... don't do it on the computer.
it's faster, cleaner, shorter... you will build a cleaner cia that will have the same hash each time (unlike the cias from makerom lol)

this is why i made FunkyCIA, so that we could have and share 'perfect'/'nearly perfect' cias, that won't cause any problems. you can redownload them from eshop.. etc. but your cias... no it's not good for the community i believe. noobs don't really understand and just use the shiny new tool.

@Plailect - why did you choose to do it this way?

 

[Xenon Hacks]

ooh yeah i just realized when i looked at the code on gitbhub... the cias this makes will not be good...
because the contents are decrypted in order to make the cia.
so, if you then want to get the same thing from the eshop, you will have problems because you will have a dirty ticket.
i think you will get than 99% error, because the stuff you download from eshop will be trying to be decrypted with the incorrect key.
if you guys really want to use keys and not share full tickets... then why aren't you sharing the encrypted key and using this to build the cia?
let the 3ds do the decryption... don't do it on the computer.
it's faster, cleaner, shorter... you will build a cleaner cia that will have the same hash each time (unlike the cias from makerom)

this is why i made FunkyCIA, so that we could have and share 'nearly perfect' cias, that won't cause any problems.

@Plailect - why did you choose to do it this way?

Thats correct but it never bothered me since i'm not gonna download it from the eShop legitimately at any point anyways maybe you two can colab since you are in fact the ticket master.

 

[cearp]

Thats correct but it never bothered me since i'm not gonna download it from the eShop legitimately at any point anyways maybe you two can colab since you are in fact the ticket master.

yes ok, but when people share them online, we want nice cias uploaded and not ones that will interfere with exiting stuff/future stuff on our consoles.
well @Ptrk25 has a nice GroovyCIA gui java program that does what FunkyCIA does, he or i both can add a little update to support encrypted title keys i guess.
it would be a nicer solution than this tool

 

[Xenon Hacks]

yes ok, but when people share them online, we want nice cias uploaded and not ones that will interfere with exiting stuff/future stuff on our consoles.
well @Ptrk25 has a nice GroovyCIA gui java program that does what FunkyCIA does, he or i both can add a little update to support encrypted title keys i guess.
it would be a nicer solution than this tool

Then setup an IRC,Git fork, and get to coding yo

 

[cearp]

Then setup an IRC,Git fork, and get to coding yo

lol that's a lot of work when i can just write a bunch of lines in 30 minutes and upload a new zip in my FunkyCIA thread

 

[liomajor]

this is why i made FunkyCIA, so that we could have and share 'nearly perfect' cias, that won't cause any problems.

To be honest, i would like the idea to extract the tickets from ticket.db and use them.

Since ticket.db was in the dark and forgotten for a long time, no one pulled off another tool to work with it since 'ticket installer'.

After rework of fbi, it's possible now to delete tickets one by one.

 

[cearp]

To be honest, i would like the idea to extract the tickets from ticket.db and use them.

Since ticket.db was in the dark and forgotten for a long time, no one pulled off another tool to work with it since 'ticket installer'.

After rework of fbi, it's possible now to delete tickets one by one.

if you want to extract the tickets you can just use FunkyCIA and tell it -nodown
maybe it's a waste to make a separate tool just for ticket extraction

 

[liomajor]

if you want to extract the tickets you can just use FunkyCIA and tell it -nodown
maybe it's a waste to make a separate tool just for ticket extraction

Indeed, but a .cia tool would be nice to handle ticket.db > exctract/inject/delete tickets.

 

[cearp]

Indeed, but a .cia tool would be nice to handle ticket.db > exctract/inject/delete tickets.

oh you mean on the 3ds itself, sure that would be nice

 

[liomajor]

oh you mean on the 3ds itself, sure that would be nice

Anyway, what has been encrypted can be crypted again. Since XhXrXng did grow, a change has to be done fast *whistle*

 

[cearp]

Since XhXrXng did grow, a change has to be done fast *whistle*

what's that?

 

[Xenosaiga]

what's that?

I'm gonna take a crack at it. Sharing. As in sharing ticket.db and titlekeys.

Was I right? Do I get a cookie?

 

[redunka]

ooh yeah i just realized when i looked at the code on gitbhub... the cias this makes will not be good...
because the contents are decrypted in order to make the cia.
so, if you then want to get the same thing from the eshop, you will have problems because you will have a dirty ticket.
i think you will get that 99% error, because the stuff you download from eshop will be trying to be decrypted with the incorrect key.
if you guys really want to use keys and not share full tickets... then why aren't you sharing the encrypted key and using this to build the cia?
let the 3ds do the decryption... don't do it on the computer.
it's faster, cleaner, shorter... you will build a cleaner cia that will have the same hash each time (unlike the cias from makerom lol)

this is why i made FunkyCIA, so that we could have and share 'perfect'/'nearly perfect' cias, that won't cause any problems.

@Plailect - why did you choose to do it this way?

^This. Totally agree, makerom certainly isn't the best way to make cia.
Dirty, can hang PC while making large cia, fails at titles that have lot of content (some DLC).

Also, I honestly can't understand, why decrypting content with Decrypt9 before making cia?
This statement is quite incorrect:

The NCCH on eShop games is encrypted and cannot be used without decryption on a 3DS.

Orginal CDNto3DS script builds cia from encrypted NCCH (and PlaiCDN actually still can do it too).
Full decryption can be useful for seed encrypted titles, but you shouldn't force people to do it
by telling them that it "cannot be used", it's not true and also useless for most of old eShop content.
People can do decryption in Decrypt9 after packing cia if they want so. Or just get seed from eShop.
Especially when this script can also create .3ds, which obviously can be used only with Gateway.
And Gateway can't handle decrypted non executable NCCH (aka CFA), so you either left them
encrypted and thus properly signed, or GW users can forget about manuals, download play and DLC.

I prefer FunkyCIA for cia backups. But CDNto3DS is useful if you want to get .3ds for eShop titles.
So it's still nice to have PlaiCDN as an option, at least for .3ds building and cool new features.

 

[Kohmei]

So is there a way to make a seeddb.bin file using the title ID and the seed? Because that seems like all you should need, and yet I have no idea how to make it. Trying to reverse seedconv right now because the process seems so simple

 

[jurassicplayer]

So is there a way to make a seeddb.bin file using the title ID and the seed? Because that seems like all you should need, and yet I have no idea how to make it. Trying to reverse seedconv right now because the process seems so simple

I already did. I made a pull request already too. If you want, you can grab it from my github until it gets merged.
https://github.com/jurassicplayer/PlaiCDN

Also if anyone wants to try batch DL/build, I have a branch that includes an improved version of liomajor's ideas. You still will need to make your own wrapper script to feed in new titles.

I kind of wanted to just leave this stuff under a rock or something until Plailect had the chance to look over the modifications and maybe merge them (since I don't want to build the exe...I just use the python script).

 

[Kohmei]

(since I don't want to build the exe...I just use the python script).

Ah, took me a while to figure that out. Thanks, this seems to work great

 

[Deleted User]

ooh yeah i just realized when i looked at the code on gitbhub... the cias this makes will not be good...
because the contents are decrypted in order to make the cia.
so, if you then want to get the same thing from the eshop, you will have problems because you will have a dirty ticket.
i think you will get that 99% error, because the stuff you download from eshop will be trying to be decrypted with the incorrect key.
if you guys really want to use keys and not share full tickets... then why aren't you sharing the encrypted key and using this to build the cia?
let the 3ds do the decryption... don't do it on the computer.
it's faster, cleaner, shorter... you will build a cleaner cia that will have the same hash each time (unlike the cias from makerom lol)

this is why i made FunkyCIA, so that we could have and share 'perfect'/'nearly perfect' cias, that won't cause any problems. you can redownload them from eshop.. etc. but your cias... no it's not good for the community i believe. noobs don't really understand and just use the shiny new tool.

Forgive my ignorance, but how does this affect 3DS>CIA conversions using something like SimpleCIA converter/makerom? Wouldn't that cause a dirty ticket as well?

 

[cearp]

Forgive my ignorance, but how does this affect 3DS>CIA conversions using something like SimpleCIA converter/makerom? Wouldn't that cause a dirty ticket as well?

yes it would, you won't be able to redownload those games etc, 'not a good cia'.
but, for some things that is necessary, some games are not released on eshop.
ideally we would have dumped eshop games, but that means someone has to buy it and dump it.
usually we have a .3ds rom dumped of games first.

 

[Deleted User]

yes it would, you won't be able to redownload those games etc, 'not a good cia'.
but, for some things that is necessary, some games are not released on eshop.
ideally we would have dumped eshop games, but that means someone has to buy it and dump it.
usually we have a .3ds rom dumped of games first.

Figured as much, so both methods (converting 3DS>CIA and CDN with this tool) would create a dirty ticket. However this can be rectified by deleting the ticket for said application?