I'm getting an error with that one that tells me I need to adjust the limits in the config if using it on a newer firmware (which I guess everyone would be doing anyway, right?) but gives me no clue how to adjust them. Do I add one to each value? Do I add 1000? Do I add 1000000000000000000000000? Do I add 98746349374683?
If you download the latest version of the program and copy the newer set of keys, you don't need setup any, all will work as is out of the box.
I did download the latest as of right before I wrote that, which, according to GitHub is 1.5.6-3 (unless there is some hidden version) and the first thing it did when I ran it was ask me to set some configuration numbers. As there is zero information provided on what to set them to I left them at the defaults and hit yes to save the default numbers it provided. This is quite a long thread and there is zero information on the GitHub, so maybe I've missed something about how to set them to something else other than what it pops up as defaults on the first run.
Right before using it, I reextracted the prod.keys from my Switch using the latest Lockpick_RCM (dated November 6 of 2022.) (eg it's a real Switch, not Yuzu or something) and renamed them appropriately to keys.dat for what this program wanted. Unless it needs them in some other format. (There is no info on the GitHub and this is quite a long thread, so maybe I've missed something about how to modify the standard key output if it requires such a thing?) Does it need anything extra like maybe stuff from the dev keys?
The error message when I attempt to generate keys using the "latest" firmware 15.0.1 is:
Exact same thing under ES2 (it says you need to run this if the previous tab failed to get keys.) I get basically the same error under the other tabs like FS -- slightly different, but basically saying the same thing. I will add here that the keydata tab shows the correct information from the prod.keys, so it did load it ok. Of course, as 15.0.1 is the current firmware, that means that any firmware this will be used on now and from now on will be greater than 15.0.0. Thus it does at least appear to be saying that setup will be needed since basically all from now and into the future will indeed be greater than 15.0.0.
Right before using it, I reextracted the prod.keys from my Switch using the latest Lockpick_RCM (dated November 6 of 2022.) (eg it's a real Switch, not Yuzu or something) and renamed them appropriately to keys.dat for what this program wanted. Unless it needs them in some other format. (There is no info on the GitHub and this is quite a long thread, so maybe I've missed something about how to modify the standard key output if it requires such a thing?) Does it need anything extra like maybe stuff from the dev keys?
The error message when I attempt to generate keys using the "latest" firmware 15.0.1 is:
Code:
Unable to decrypt, did you update your keys?
Try adjusting the ES size limits in the config settings if firmware is greater than 15.0.0.you should use the firmware from darts site or the github of THZoria
exctract the rar files on a folder and pass that folder for processing.
exctract the rar files on a folder and pass that folder for processing.
I did.
It seems actually the problem was something overwrote my manual update of Lockpick_RCM.bin with an older version (ironic since I had manually updated it before,) so it was not extracting a newer key apparently. You really can't trust those automatic updaters everyone swears by. It seems like Lockpick_RCM generates the newer key correctly now.
One thing I want to double check on. It says that you're required to install Visual Studio. I misread that and thought it was saying the latest runtimes. I do not have Visual Studio installed and it seems to work. I consider that an unreasonable requirement as Visual Studio is huge and requires a lot of setup. (Some of us don't have super large SSDs.) Is it actually officially required?
It seems actually the problem was something overwrote my manual update of Lockpick_RCM.bin with an older version (ironic since I had manually updated it before,) so it was not extracting a newer key apparently. You really can't trust those automatic updaters everyone swears by. It seems like Lockpick_RCM generates the newer key correctly now.
One thing I want to double check on. It says that you're required to install Visual Studio. I misread that and thought it was saying the latest runtimes. I do not have Visual Studio installed and it seems to work. I consider that an unreasonable requirement as Visual Studio is huge and requires a lot of setup. (Some of us don't have super large SSDs.) Is it actually officially required?
Similar threads
- No one is chatting at the moment.
-
-
-
@
Veho:
Once again I fell down the martial arts rabbit hole and am plumbing the murky depths of the internet's various martial arts and fighting crafts echo chambers. -
@
Veho:
I like to get up to speed on that every now and then, see what the newest high wisdom everyone is spouting nowadays.
-
@
Veho:
If you're not actively involved and only get up to speed every few years or so, you can see the tide of public opinion flapping worse than my dong while I'm skipping naked down a hallway.
-
-
-
-
@
Veho:
Like most forced updates, this one has terrible support and was very poorly received by the userbase.
-
-
-
-
-
-
@
FAST6191:
How do you know the giant wasn't on walkabout https://c8.alamy.com/comp/ADKT2C/ce...carving-in-dorset-uk-thought-to-be-ADKT2C.jpg -
@
Veho:
That's what I said, maybe they were just doing a recreation of the Cerne Abbas giant but didn't finish it in time.
-
-
-
-
-
-
-
@
Psionic Roshambo:
https://imgur.com/gallery/ZfBfPgk 100 million... Can think of better uses but OK lol -
-
