The trouble with the seeddb updater from the list I posted above .Which entry?
The trouble with the seeddb updater from the list I posted above .Which entry?
Hmm I'm not following. lol BUT it is 6 am and I'm tired...so yeah. :/The trouble with the seeddb updater from the list I posted above .
9.30pm ( ͡° ͜ʖ ͡°)Hmm I'm not following. lol BUT it is 6 am and I'm tired...so yeah. :/
Saves are prolly on SD, so I'd say anything installed will be on SD but not considered installed by system and settings changes will be undone.Hello, is the emuNAND injection without risk if I want to insert a 2days younger same emuNAND backup to replace the actual one? I received the update nag and browser block yesterday. And what will I lose? todays gamesaves will be replaced with their state two days ago?
I installed A9LH so I just make AuReinand boot directly into sysNAND by default and then I hold L to enter my 9.2 emuNAND and use Decrypt9 just fine.Guys, I hope you can help me with this:
I installed A9LH and now I want to install TWLFirm on both emunand and sysNand. The problem is with sysnand, because when I load decrypt9WIP with A9LH directly, I get an error when I try to extract h&s from sysnand. I also tried to launch AuReinand in sysnand mode by pressing R, it launched fine, launched homebrew menu using ninjhax but when I try to launch decrypt9 or any other app, it just returns me to the homebrew menu again, I don't know why this happens.
Guys, I hope you can help me with this:
I installed A9LH and now I want to install TWLFirm on both emunand and sysNand. The problem is with sysnand, because when I load decrypt9WIP with A9LH directly, I get an error when I try to extract h&s from sysnand. I also tried to launch AuReinand in sysnand mode by pressing R, it launched fine, launched homebrew menu using ninjhax but when I try to launch decrypt9 or any other app, it just returns me to the homebrew menu again, I don't know why this happens.
I installed A9LH so I just make AuReinand boot directly into sysNAND by default and then I hold L to enter my 9.2 emuNAND and use Decrypt9 just fine.
This happens because some stuff required for decryption is not (yet?)
No one (to my knowledge) is working on that at the moment.Just curious, do you know any of the devs working on making this happen? I would like to follow their postings and work, if available.
I think it would be better to have a small command line utility to generate the enctitlekeys.bin from human readable data (textfile for example). You won't get a virtual keyboard on ARM9, and implementing a different input method would be a pain in the ass too .@d0k3 , can you add a way for us to input data (title id, common key index and encrypted title key) directly into Decrypt9 and have the decrypted titlekey outputted to the screen?
It's kinda annoying always having to make that "enctitlekeys.bin" when we want titlekys for stuff that 's not installed.
Even if it had a simple password screen style, where we select the letters one by one, like in old games, would already be enough.I think it would be better to have a small command line utility to generate the enctitlekeys.bin from human readable data (textfile for example). You won't get a virtual keyboard on ARM9, and implementing a different input method would be a pain in the ass too .
Asking this... what would be the source of your input data (title id, common key index and encrypted title key)? Any manual input method with these long numbers would be tedious and very error prone, leading to more frustration than good I think.Even if it had a simple password screen style, where we select the letters one by one, like in old games, would already be enough.
Even if we had to just select the positions with left and right and change the digits with up and down it would already be cool, heheh
We can get that info from a legitimate ticket, or even from a CIA made from NUS content with make_cdn_cia (Decrypt9 couldn't handle these last time I tried, by the way).Asking this... what would be the source of your input data (title id, common key index and encrypted title key)? Any manual input method with these long numbers would be tedious and very error prone, leading to more frustration than good I think.
For legitimate tickets, there is already the print_ticket_keys.py script (included in Decrypt9). For CIAs, I guess make_cdn_cia doesn't lend itself to automation (ie, build a enctitlekeys.bin), but putting something together for the PC commandline is not too difficult. I agree that for single keys, putting it in directly might be a tad faster then moving around files.We can get that info from a legitimate ticket, or even from a CIA made from NUS content with make_cdn_cia (Decrypt9 couldn't handle these last time I tried, by the way).
I know the title key is kinda long but as long as you add spaces between its bytes it wouldn't be too much trouble.
Knows more about what? I don't pop in too often any more.For legitimate tickets, there is already the print_ticket_keys.py script (included in Decrypt9). For CIAs, I guess make_cdn_cia doesn't lend itself to automation (ie, build a enctitlekeys.bin), but putting something together for the PC commandline is not too difficult. I agree that for single keys, putting it in directly might be a tad faster then moving around files.
As for CIAs from NUS, made by make_cdn_cia... I'd need an example, and you should better doublecheck it. I recently checked the FW 1.0.0 (US) package (created from a valid NAND backup). Seven files could not be decrypted, but doublechecking these with NUS content it turned out the non-decryptable CIAs had broken contents (100% sure, cause matching hashes and differing files). Maybe @MassExplosion213 knows more?