How about you figure it out yourself, instead of being spoonfed!Could you perhaps make some constructive suggestions instead of constantly being an asshole?
I even gave you a clue lol.
I helped you already...
Last edited by cearp,
How about you figure it out yourself, instead of being spoonfed!Could you perhaps make some constructive suggestions instead of constantly being an asshole?
cearp is a gender neutral username and his profile is private.(Going off topic here).
Honestly I'm always annoyed when they assume I'm male even though I have "Aurora" (which is my real name btw) as part of the username, and I even have my profile set to female, just because I can write some code. I'm sure if everything was switched (everyone being assumed female by default, even when the signs point to otherwise) and it happened to you you'd be annoyed too.
Everything in this statement is a lie. Buy a mirror.See virtually all my other posts, I'm decent. Just this guy thinks he is always right. I actively choose to be unhelpful to people like that. Apart from that, I'm nice and helpful
And no need to work together etc... my tool is done, nothing to gain really. I didn't even realize I was posting in this thread! I thought I was posting the clue in mine lol
dank. grief.And frankly I could not give a single ****.
dank. grief.
username checks out.
... I actively choose to be unhelpful to people like that. Apart from that, I'm nice and helpful
The issue with using makerom and decrypted keys, is if someone installs a CIA they did not purchase, then later decides to do so, they will not be able to download their now purchased game from the eShop. Regardless that @cearp is being a hard ass about the whole situation he does have a point when it comes to the final CIA output.I rest my case. No need to reply to trolls (sorry dank ). cearp, you're not helping your case with comments like these.
Also,
This doesn't help your case (sorry, this seems contradictory). I'm of the philosophy of help people regardless and let their flippant behavior drag them down, but maybe that's just the way I was raised. All of the banter back and forth is off-putting.
Frankly, from what I understand from both scripts, the core difference is the handling of the title keys with regards to the generated CIAs. As I understand it, FunkyCIA requires the encrypted titlekey to generate a CIA that can then be repaired/restored by eshop-- this implies a user has said encrypted title key, meaning they bought the game (frankly, as they should have). PlaiCDN doesn't require the encrypted titlekey, and due to makerom being unable to re-encrypt the titlekey (due to not having access on PC to slot 0x3d for keyx I think?), it does use a dummy key in the CIA generation, meaning said created CIAs can't be repaired or obtained from eshop. On the other hand, these CIAs can be created without having to use the 3ds except to install them. I see two slightly different use cases, and fail to see why there needs to be continued arguing.
The issue with using makerom and decrypted keys, is if someone installs a CIA they did not purchase, then later decides to do so, they will not be able to download their now purchased game from the eShop. Regardless that @cearp is being a hard ass about the whole situation he does have a point when it comes to the final CIA output.
No, the invalid TitleKey in the makerom version of the CIA is permanently entered into your console's title.db file, which is used when downloading titles from the eShop. Subsequent installs of the same title but with different TitleKey's do not overwrite the bad entry. So when the eShop goes to install the title after downloading it (at the 99% mark) it will attempt to decrypt it using this invalid TitleKey and fail. If you install a CIA with an invalid TitleKey, you are forever stuck with installing CIA's of that title. Even if you format your 3DS, title.db remains.Yep. There is a difference between the two due to makerom. If people want to buy the game legitimately later, can't they just delete the current CIA via FBI or their CIA manager of choice? I mean, it's less convenient (use JK Save manager to back up saves I guess), but it is a valid workaround. I would probably suggest to Plailect to outline these limitations in his README.
No, the invalid TitleKey in the makerom version of the CIA is permanently entered into your console's title.db file, which is used when downloading titles from the eShop. Subsequent installs of the same title but with different TitleKey's do not overwrite the bad entry. So when the eShop goes to install the title after downloading it (at the 99% mark) it will attempt to decrypt it using this invalid TitleKey and fail. If you install a CIA with an invalid TitleKey, you are forever stuck with installing CIA's of that title. Even if you format your 3DS, title.db remains.
This is kind of true, best I can tell it marks the TitleKey so that it can be overwritten but doesn't actually delete it. For example, if you delete a TitleKey with FBI v2, then dump your TitleKeys, it'll still be there. But if you then install a title that uses a different TitleKey, it will overwrite the old entry. That's as best as I've been able to figure it out. It's good that at least even this method exists though, just don't system transfer to a stock 3DS or accidentally break your hack.FBI can delete said title key as well, at least with the recent release. So that is a solution, albeit a more manual on since you would need to figure out which is the right one you'd have to delete.
Alright, here we go. I'm not forking this on Github because it's literally thrown together from bits and pieces and heavy deletions from the original PlaiCDN script. There's probably a lot of cleanup to be done but I wanted to put this out there so people could use it.<snip>
PlaiCDN can still perform its Title Name and region lookup using encTitleKey.bin with a few modifications to the -deckey flag, so I'm currently looking at a way to merge the two's functionality and ultimately output a CSV that can be imported into Excel or MySQL databases.
I found a way to download the icon.bin from the nintendo servers, it cointains the gameicon, titlename, publisher and region. PM me if you're interested.@cearp I found the Region detection by product code, however I can't get rid of the for loop that checks all the ninja servers since additional information comes from there such as publisher, version, file size and the product code itself. I still implemented a new region detector that helps properly identify region-free games that were identifying as EUR for some reason.
Cool analogman, the final letter of the product code is the region.
I found a way to download the icon.bin from the nintendo servers, it cointains the gameicon, titlename, publisher and region. PM me if you're interested.
So this program checks if the titlekeys are valid?Also take a look at this: https://github.com/HouseBreaker/NintendoCDN-TicketParser
So this program checks if the titlekeys are valid?
(lol it's using groovycia's database)
EDIT: Oh I see, it already downloads the icon.bin