Homebrew RELEASE Lockpick - Switch key derivation homebrew

  • Thread starter Thread starter shchmue
  • Start date Start date
  • Views Views 197,356
  • Replies Replies 303
  • Likes Likes 58
we spoke on Discord but for those playing at home, i'll be pushing a fix for Lockpick not finding TSEC keys dumped with Hekate 4.8, i had a strict file size check in place and Hekate rightfully changed the file size for it.

Thanks shchmue.
Does Lockpick require any other update to support 7.0.x keys?
 
1.2.1 is out:

  • Generate bis keys without master keys
  • Update file size check to support Hekate v4.8 TSEC dump
  • Fixed prod.keys alphabetization error
  • Fixed build warning for ff.c
  • Added in-app disclaimer about which keys can be dumped

https://github.com/shchmue/Lockpick/releases/tag/v1.2.1


Thanks shchmue.
Does Lockpick require any other update to support 7.0.x keys?
probably won't be able to support 07 keys at all in Homebrew, working on a payload that can though.
 
Thanks for the tips guys.
Kosmos have been updated again, now they updated Lockpick too.
I didn't get any errors while dumping the keys at 7.0.x now ^^
 
Thanks for the tips guys.
Kosmos have been updated again, now they updated Lockpick too.
I didn't get any errors while dumping the keys at 7.0.x now ^^

It's not returning an error (fixes compatibility with Hekate 4.8) but current version of Lockpick is not able to extract all needed keys on firmware 7.0.x.
Shchmue is working on a new software approach (using payloads) that could extract all keys but it will take time.
So be patient.
 
Last edited by 8BitWonder,
  • Like
Reactions: MK73DS
I have some troubles to get a valid prod.keys (keys.dat) file. I have been used Lockpick on my previous 6.2 machine to generate those keys, nowadays I am operating 7.0.1 w/ Atmos 8.4.0 . XCI installer or Nro2Nsp seems not to work in my case. Do I have to do additional steps depending of each application?
 
  • Like
Reactions: Lacius and hausa51
I'm on 6.2 and used the newest Lockpick to generate keys.
All keys look fine (and tested against my rawnand.bin with hacdiskmount) except biskey 0, which contains a string of 0's about 8 bytes long for both Crypto and Tweak. (ex: 206db4d8040000000000...). Obviously, this is incorrect. Should I just try dumping the keys again, and what could have caused this error?
 
I'm on 6.2 and used the newest Lockpick to generate keys.
All keys look fine (and tested against my rawnand.bin with hacdiskmount) except biskey 0, which contains a string of 0's about 8 bytes long for both Crypto and Tweak. (ex: 206db4d8040000000000...). Obviously, this is incorrect. Should I just try dumping the keys again, and what could have caused this error?
That's unusual. I'd advise re-downloading the latest Lockpick and/or moving on to Lockpick_RCM.

Just pushed version 1.2.2 for Lockpick_RCM cross-compatibility
https://github.com/shchmue/Lockpick/releases
  • Do not overwrite existing keyfile that contains master_key_07
  • Read eticket_rsa_kek from existing keyfile in case user is only running this for titlekeys
  • Create /switch folder if needed
 
That's unusual. I'd advise re-downloading the latest Lockpick and/or moving on to Lockpick_RCM.

Just pushed version 1.2.2 for Lockpick_RCM cross-compatibility
https://github.com/shchmue/Lockpick/releases
  • Do not overwrite existing keyfile that contains master_key_07
  • Read eticket_rsa_kek from existing keyfile in case user is only running this for titlekeys
  • Create /switch folder if needed
I'll check into that release, many thanks.
 
If I use Lockpick RCM on 7.0.1, will it dump all the current keys? Or do I need to run Lockpick as homebrew on pre 6.2, grab some keys, then run on 6.2+?
 
That's unusual. I'd advise re-downloading the latest Lockpick and/or moving on to Lockpick_RCM.

Just pushed version 1.2.2 for Lockpick_RCM cross-compatibility
https://github.com/shchmue/Lockpick/releases
  • Do not overwrite existing keyfile that contains master_key_07
  • Read eticket_rsa_kek from existing keyfile in case user is only running this for titlekeys
  • Create /switch folder if needed
Just an update:
-Ran Lockpick 1.2.2, had the same problem with biskey 0 (more 0's this time, in fact)
-Ran new Lockpick_RCM and the biskey 0 key was generated correctly!
Strange and hopefully isolated case.
Thanks again!
 
Hey guys, new member, running SX OS emuNAND on 6.2, and my sysNAND is updated to 7.0.1. I understand now that getting my Tegra keys will be up to TX at this point, and I'll have to wait on my XCI conversions.
Many of you answered many of my questions, but one remains:

When using the Hekate payload, what (if any) modifications does Hekate make to sysNAND to generate my keys? I'm trying to enjoy the best of both worlds here, and allow for online play on my clean sysNAND (working so far!). Obviously I want to be as safe as possible, and I don't want to get banned when I play my legit eshop and cartridge games online. Thanks in advance for any insight you may have!
 
Hey guys, new member, running SX OS emuNAND on 6.2, and my sysNAND is updated to 7.0.1. I understand now that getting my Tegra keys will be up to TX at this point, and I'll have to wait on my XCI conversions.
Many of you answered many of my questions, but one remains:

When using the Hekate payload, what (if any) modifications does Hekate make to sysNAND to generate my keys? I'm trying to enjoy the best of both worlds here, and allow for online play on my clean sysNAND (working so far!). Obviously I want to be as safe as possible, and I don't want to get banned when I play my legit eshop and cartridge games online. Thanks in advance for any insight you may have!
The only modification Hekate can make to the SysNAND is with AutoRCM. Everything else is either directed towards the SD card (fix SD files attributes) or the battery (de-sync battery fix). Dumping keys =/= writing to the NAND.
 
  • Like
Reactions: Alchemy_Gaming
Hey guys, new member, running SX OS emuNAND on 6.2, and my sysNAND is updated to 7.0.1. I understand now that getting my Tegra keys will be up to TX at this point, and I'll have to wait on my XCI conversions.
Many of you answered many of my questions, but one remains:

When using the Hekate payload, what (if any) modifications does Hekate make to sysNAND to generate my keys? I'm trying to enjoy the best of both worlds here, and allow for online play on my clean sysNAND (working so far!). Obviously I want to be as safe as possible, and I don't want to get banned when I play my legit eshop and cartridge games online. Thanks in advance for any insight you may have!
just use this it'll get them all https://gbatemp.net/threads/switch-7-0-key-derivation-lockpick_rcm-payload.532916/ and it doesn't write anything to nand
 
  • Like
Reactions: Alchemy_Gaming

Site & Scene News

Popular threads in this forum