Homebrew RELEASE Lockpick - Switch key derivation homebrew

  • Thread starter Thread starter shchmue
  • Start date Start date
  • Views Views 197,519
  • Replies Replies 303
  • Likes Likes 58
I found keys, but now i get a "section 0 is corrupted" and "section 1 is corrupted". What does it mean?
from hactool? it means you're issuing the wrong arguments to hactool or else you didn't have high enough firmware installed to get keys that match the file you're trying to decrypt
 
I just updated my firmware to 9.0 and updated atmosphere to latest and I never had an issue before with lockpick rcm dumping keys but it seems im getting corruption on dumping.

the prod.keys starts out like this

€…s‰½^?ì›ÊËBÿ@ÑÛØ\IÑ“-‰Ž·Ý6ƒóv
Am®ò„«³8裴Ëý)ÂŠ¢'€Í
TŠ£[Ç<žI%™?ý‹’[b”*ïHc|>ÝF/²G=ˆXLñÆ
uOÏ} ¼‡tý´4a(HTÚ€õ‰×fïúÃ"òÒˆxCMs'¼æŸDŽsäMÖ\(˜Lnsëcxþ‚Û – º^sï¥ùaes_kek_generation_source =

any idea whats causing this?

edit: using 1.5.0 does not cause this problem and everything is working good now
 
Last edited by TakaOni,
I just updated my firmware to 9.0 and updated atmosphere to latest and I never had an issue before with lockpick rcm dumping keys but it seems im getting corruption on dumping.

the prod.keys starts out like this

€…s‰½^?ì›ÊËBÿ@ÑÛØ\IÑ“-‰Ž·Ý6ƒóv
Am®ò„«³8裴Ëý)ÂŠ¢'€Í
TŠ£[Ç<žI%™?ý‹’[b”*ïHc|>ÝF/²G=ˆXLñÆ
uOÏ} ¼‡tý´4a(HTÚ€õ‰×fïúÃ"òÒˆxCMs'¼æŸDŽsäMÖ\(˜Lnsëcxþ‚Û – º^sï¥ùaes_kek_generation_source =

any idea whats causing this?

edit: using 1.5.0 does not cause this problem and everything is working good now
are you saying 1.6.0 gave that output or an older version?

edit: i figured it out, try 1.6.1
 
Last edited by shchmue,
  • Like
Reactions: TakaOni
@shchmue I'm running SXOS, sysnand at 5.1.0, and EmuNAND at 9.0.1, using latest github release of Lockpick RCM the ability to export from Emunand is shown, but not selectable, it shows a message at the bottom of the screen that no eemc config present.

I copied sept folder from Kosmos on mt SDCard, have I missed something else that's required?

I'm unsure what to do, can anyone give any direction please?
 
@shchmue I'm running SXOS, sysnand at 5.1.0, and EmuNAND at 9.0.1, using latest github release of Lockpick RCM the ability to export from Emunand is shown, but not selectable, it shows a message at the bottom of the screen that no eemc config present.

I copied sept folder from Kosmos on mt SDCard, have I missed something else that's required?

I'm unsure what to do, can anyone give any direction please?

Just read through the RCM thread and saw that SXOS emunand is not supported, so I figure thats why...
 
I successfully dumped my title.keys (about 316 keys), renamed it to keys.ini and dropped it into the folder containing NCA/NSP extractor but every single key fails to match when I attempt to extract Pokemon Sword to LayeredFS. What am I doing wrong/missing? I just want to change some textures ):
 
I successfully dumped my title.keys (about 316 keys), renamed it to keys.ini and dropped it into the folder containing NCA/NSP extractor but every single key fails to match when I attempt to extract Pokemon Sword to LayeredFS. What am I doing wrong/missing? I just want to change some textures ):

you need prod.keys not the title.keys. If you are in latest sysnand, use lockpick rcm
 
  • Like
Reactions: Slothbox
you need prod.keys not the title.keys. If you are in latest sysnand, use lockpick rcm
I appreciate you, however I'm still having a bit of issue. So I rebooted back into Hekate, and ran the payload Lockpick_RCM however I just get the error "unknown pkg1 version"
 
I'm trying to use ChoiDuJour. I got all the keys I need from the lockpick_rcm prod.key file except for the header key. Is there another program that I need to use to find the header key?
 
I'm trying to use ChoiDuJour. I got all the keys I need from the lockpick_rcm prod.key file except for the header key. Is there another program that I need to use to find the header key?
did lockpick_rcm give any errors? one thing that would cause that is if your pkg2 is hosed which is of course a reason you might be using Choi in the first place...
 
When I use Lockpick_rcm 1.8.1 it says keyblobs 1-5 are corrupt and unable to derive Package2 key.
Any ideas? My switch wont boot.

--------------------- MERGED ---------------------------

Im currently on FW 6.1.0
 
When I use Lockpick_rcm 1.8.1 it says keyblobs 1-5 are corrupt and unable to derive Package2 key.
Any ideas? My switch wont boot.

--------------------- MERGED ---------------------------

Im currently on FW 6.1.0
Keyblobs are probably fucked. Regenerate them, or update to 6.2.0 or higher.
 
Do you know if there is a guide that explains regenerating keyblobs? I can't seem to find the information.
https://github.com/MegatonHammer/linkle
You need your tsec key, your sbk, and some non-console-unique keys. Usage for keygeneration is “linkle keygen” or something like that, if you have the right keys it’ll give you encrypted keyblobs, you’ll have to manually hex edit those into your boot0.

It’s probably just easier to update to a later firmware.
 

Site & Scene News

Popular threads in this forum