Tutorial  Updated

How to get Switch Keys for Hactool/XCI Decrypting

This thread is deprecated
For a faster, easier and more up-to-date way of getting keys use Lockpick_RCM by shchmue
If you still want to follow this tutorial and end up with less keys, continue reading the Thread.


WARNING
  • DO NOT GIVE OUT ANY OF YOUR KEYS TO ANYONE! I CANNOT STRESS THAT ENOUGH!
  • DO NOT SHARE YOUR KEYS BETWEEN MULTIPLE SWITCHES THAT YOU DO/DON'T OWN! SOME ARE CONSOLE-UNIQUE
  • DO NOT ASK ME FOR KEYS


LEGEND
  • SBK
    SecureBootKey
  • TSEC
    Tegra Security Co-processor Key
  • eMMC
    Embedded MultiMediaCard (Switch's Onboard Storage)


GOAL
End up with 83+ keys including SBK and TSEC keys. Get Master Key's 0-5. (Master Keys 6 onwards is not done in this tutorial)
Reminder, if you want more up-to-date and much more convenient way to get your Switch's Keys, use Lockpick by shchmue (available in nx-appstore/homebrew store)


Tutorial — (Outdated for Switch's on firmware 6.x or newer)


#1 - Dumping System Keys (Biskeydump)#2 - Dumping Required Files#3 - Hactool Preparation#4 - Dumping KeysFinal WordsTroubleshooting


  1. We need to get your Secure Boot Key (SBK) and Tegra Security Co-processor Key (TSEC) before we can get the main keys.
    These are 100% console unique.

    1. Download and extract biskeydump.bin from biskeydumpvx.zip
      - Follow this tutorial but instead of using CTCaer's Hekate Mod .bin file, use the biskeydump.bin file
      - If the QR Code is Blue, Scan the QR Code with your Phone, Laptop e.t.c
      - If you cant find a device you can scan with, type them out into your PC/Laptop (Its highly recommended to scan the QR Code, as a lot of characters can look like another, O0, Il, rn can look like m, e.t.c)
    2. Once you have the biskeydump of your System, store all the keys you received somewhere safe, I recommend a secure cloud storage aswell as a USB Stick, perhaps even print it.
      - Don't give this to ANYONE, Seriously.

    If you get any errors please go to the Troubleshooting Tab.


    1. Follow this tutorial AGAIN but this time use CTCaer's Hekate Mod.
      - "Tools" -> "Backup..." -> "Backup eMMC BOOT0/1"
      - "Tools" -> "Backup..." -> "Backup eMMC SYS"
      - Back all the way to the first menu, and choose "Power off"
    2. Take the microSD Card out of your Switch and into your PC.
    3. Copy both "BOOT0" and "BCPKG2-1-Normal-Main" from "sd:/backup/xxxxxx/" (xxxxxx is different for everyone) to "hactool" on your Desktop (create the "hactool" folder)
      - Rename them with .bin at the end, "BOOT0.bin", "BCPKG2-1-Normal-Main.bin"

    1. Download and install Python 2.7.x - NOT Python 3.x.x
      When installing, it will ask you what features you want installed, scroll to the bottom and make sure "Add Python to Path" has "Entire Feature Installed to HDD" option chose (No Red X Icon), otherwise the scripts wont find Python and WILL fail
    2. Download and extract hactool TO THE DESKTOP AND NAME THE FOLDER "hactool"
      On Linux/MacOS: clone and build hactool manually
    3. Right-click this (script originally by tesnos6921, patched by shadowninja108, jakibaki and shchmue)
      - Click "Save link as" / "save as"
      - Set "Save as type" to "All Files"
      - Name it "keys.py"
      And finally save it to the hactool folder you placed in the Desktop.
      NOTICE TO GBATEMP STAFF: The "keys" inside this file, are NOT keys, they are SHA digest hashes used to search through files to find text that matches, which would be the keys.

    1. Press WIN(Btn)+R to open "Run", type "cmd" and press Ctrl+Shift then Enter to open Command Prompt as an Administrator
    2. Type (in order) or Copy the following and paste into Command Prompt (Some Windows Versions use Right Click to Paste, some use CTRL+C)
      python -m pip install --upgrade pip
      pip install lz4
      cd Desktop/hactool

      python keys.py SBK_Here_From_Biskeydump TSEC_Here_From_Biskeydump
    3. It should say: "Now you can do hactool --keyset=keys.txt to use them!", if it does, and there's no warning messages, you're good to go! :O
    If you get any errors please go to the Troubleshooting Tab.

  2. You now have a keys.txt file with your console-specific keys inside.
    Rename as needed by any software that requires a different name or file extension, it doesn't matter.
    Though I highly recommend renaming it to prod.keys as this filename for Key file's is becoming a popular choice with other software
    There may be more keys, as the Switch's lifecycle goes on, more and more keys will be needed as the firmwares grow and grow.
    • The Hactool warning:
      Code:
      [WARN] prod.keys does not exist.
      can be safely ignored.
      - if you want to place your "keys.txt" file their, put "keys.txt" on your Desktop and run the following with Administrator Command Prompt (Step #4.1 for instructions):
      Code:
      mkdir -p %USERPROFILE%\.switch
      move "%USERPROFILE%\Desktop\keys.txt" "%USERPROFILE%\.switch\prod.keys"

  3. #1 ISSUES:
    • Code:
      Red QR Code Outline
      - The reasons this can occur is quite a rarity, all I can say is to keep rebooting and trying again.
      - If there's a new version of biskeydump out, try using the newer biskeydump.bin
    • Code:
      QR Code not being scanned by your Reader
      - Align your QR Code Readers alignment overlay with the Blue Square's Corners/Edges, NOT the QR Code's Corners/Edges.
      - Clean your camera lens
      - Be in a bright room

    #4 ISSUES:
    • Code:
      File "keys.py", line ...
      print message
      ^
      SyntaxError: Missing parentheses in call to 'print'. Did you mean print(message)?
      - You didn't place SBK and TSEC in the 4th line of the Command in Step #4.2
      - You installed Python 3.x.x when you must use 2.7.x, uninstall python, logout of windows (important it removes python from PATH) and follow Step #3.2 then move back to #4.1
    • Code:
      import lz4.block
      File "C:\Python27\lib\site-packages\lz4\__init__.py", line 17, in <module>
      from ._version import ( # noqa: F401
      ImportError: DLL load failed: The specified module could not be found.
      - The 2nd line of the Command in Step #4.2 failed without you noticing. Try running the 1st line to upgrade pip and if that goes successfully run the 2nd line to install lz4 and see if it successfully installs.
 
Last edited by shchmue,

jacobfernando

Active Member
Newcomer
Joined
Jun 26, 2018
Messages
26
Trophies
0
Age
39
XP
73
Country
United Kingdom
Hello,


hi im on 2.3.0
when you say comment the following line does it mean to add it? because is already on the script.

i get the cant find the key..... error

but when i delete the lines i get keyblob is invalid.

I have had the same problem, and I think I have solved it.

The problem is in the script, which tries to find keys "keyblob_key_source_xx" from higher versions of the firm, and if it does not find them it gives the error: "Could not find keyblob_key_source_xx! Please check the integrity of the data used in the current stage!".

keyblob_key_source_00 is for master_key_00, which is the firmware version 1.0.0-2.3.0, the others keyblob_key_source_xx do not exist in these firmware versions.

More information about the keys: "https: //gist. github. com /roblabla/d8358ab058bbe3b00614740dcba4f208" (delete spaces)


The quick solution (only for versions 1.0.0-2.3.0),

comment the following lines (366 and 367):

Code:
keyblob_key_source_id, keyblob_key_source_xx = checkfound(find_via_hashset(PKG11_data, KEY_HASHES["keyblob_key_sources"], KEY_SIZES["keyblob_key_sources"]), "keyblob_key_source_xx")
keyz[keyblob_key_source_id] = keyblob_key_source_xx

result:

Code:
#keyblob_key_source_id, keyblob_key_source_xx = checkfound(find_via_hashset(PKG11_data, KEY_HASHES["keyblob_key_sources"], KEY_SIZES["keyblob_key_sources"]), "keyblob_key_source_xx")
#keyz[keyblob_key_source_id] = keyblob_key_source_xx



Bye. :grog:
 

CKkio23

Well-Known Member
Newcomer
Joined
Jun 17, 2018
Messages
93
Trophies
0
Age
79
XP
397
Country
United States
Using BOOT0.bin to get keys from package1...
Deriving keys...
Decrypting package1...
Using Secure_Monitor.bin to get keys to decrypt package2...
Decrypting package2...
Error: Package2 Header is corrupt!
Decompressing spl.kip1 and FS.kip1...
Traceback (most recent call last):
File "keys.py", line 409, in <module>
SPL_KIP1_f = open("ini1/spl.kip1", "rb")
IOError: [Errno 2] No such file or directory: 'ini1/spl.kip1'

Is my backup corrupted? because hactool reads it fine? did the tut correct.
 
  • Like
Reactions: Boriskr

jacobfernando

Active Member
Newcomer
Joined
Jun 26, 2018
Messages
26
Trophies
0
Age
39
XP
73
Country
United Kingdom


now i get this error


Using BOOT0.bin to get keys from package1...
Deriving keys...
[ WARN ] Keyblob MAC 00 is invalid. Are SBK/TSEC key correct?
Decrypting package1...
Failed to decrypt PK11! Is correct key present?
Using Secure_Monitor.bin to get keys to decrypt package2...
Traceback (most recent call last):
File "keys.py", line 390, in <module>
TZ_f = open("package1/Secure_Monitor.bin", "rb")
IOError: [Errno 2] No such file or directory: 'package1/Secure_Monitor.bin'
 

kokoxp

Member
Newcomer
Joined
Jun 26, 2018
Messages
14
Trophies
0
Age
39
XP
86
Country
Spain
now i get this error


Using BOOT0.bin to get keys from package1...
Deriving keys...
[ WARN ] Keyblob MAC 00 is invalid. Are SBK/TSEC key correct?
Decrypting package1...
Failed to decrypt PK11! Is correct key present?
Using Secure_Monitor.bin to get keys to decrypt package2...
Traceback (most recent call last):
File "keys.py", line 390, in <module>
TZ_f = open("package1/Secure_Monitor.bin", "rb")
IOError: [Errno 2] No such file or directory: 'package1/Secure_Monitor.bin'


The SBK and TSEC keys that you passed to keys.py are correct?, Because that can be the error.

I have 2.1.0 and it works perfectly.

Code:
python keys.py ReplaceMeWithSBK ReplaceMeWithTSEC


EXAMPLE ( SBK = 1111111111111111111 and TSEC = 2222222222222222222):
Code:
python keys.py 1111111111111111111 2222222222222222222
 

jacobfernando

Active Member
Newcomer
Joined
Jun 26, 2018
Messages
26
Trophies
0
Age
39
XP
73
Country
United Kingdom
The SBK and TSEC keys that you passed to keys.py are correct?, Because that can be the error.

I have 2.1.0 and it works perfectly.

Code:
python keys.py ReplaceMeWithSBK ReplaceMeWithTSEC


EXAMPLE ( SBK = 1111111111111111111 and TSEC = 2222222222222222222):
Code:
python keys.py 1111111111111111111 2222222222222222222


yes i did that, maybe something on the script? do not know then
 

kokoxp

Member
Newcomer
Joined
Jun 26, 2018
Messages
14
Trophies
0
Age
39
XP
86
Country
Spain
yes i did that, maybe something on the script? do not know then

I can reproduce that error by executing the script with some invalid keys:

Code:
debian:~/Descargas/hactool-1.1.0$ python keys.py AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
Using BOOT0.bin to get keys from package1...
Deriving keys...
[ WARN ] Keyblob MAC 00 is invalid. Are SBK/TSEC key correct?
Decrypting package1...
Failed to decrypt PK11! Is correct key present?
Using Secure_Monitor.bin to get keys to decrypt package2...
Traceback (most recent call last):
  File "keys.py", line 391, in <module>
    TZ_f = open("package1/Secure_Monitor.bin", "rb")
IOError: [Errno 2] No such file or directory: 'package1/Secure_Monitor.bin'


Obtain the SBK and TSEC_KEY keys again from the Switch and check that they are OK.

P.D.:
Surely you have already created a file called keys.txt in the directory where we execute the script with part of the keys obtained.
 

jacobfernando

Active Member
Newcomer
Joined
Jun 26, 2018
Messages
26
Trophies
0
Age
39
XP
73
Country
United Kingdom
I can reproduce that error by executing the script with some invalid keys:

Code:
debian:~/Descargas/hactool-1.1.0$ python keys.py AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
Using BOOT0.bin to get keys from package1...
Deriving keys...
[ WARN ] Keyblob MAC 00 is invalid. Are SBK/TSEC key correct?
Decrypting package1...
Failed to decrypt PK11! Is correct key present?
Using Secure_Monitor.bin to get keys to decrypt package2...
Traceback (most recent call last):
  File "keys.py", line 391, in <module>
    TZ_f = open("package1/Secure_Monitor.bin", "rb")
IOError: [Errno 2] No such file or directory: 'package1/Secure_Monitor.bin'


Obtain the SBK and TSEC_KEY keys again from the Switch and check that they are OK.

P.D.:
Surely you have already created a file called keys.txt in the directory where we execute the script with part of the keys obtained.

gracias ya las tengo
 

LeMageFro

Well-Known Member
Member
Joined
Mar 29, 2018
Messages
215
Trophies
0
XP
1,396
Country
France
Hello,






I have had the same problem, and I think I have solved it.

The problem is in the script, which tries to find keys "keyblob_key_source_xx" from higher versions of the firm, and if it does not find them it gives the error: "Could not find keyblob_key_source_xx! Please check the integrity of the data used in the current stage!".

keyblob_key_source_00 is for master_key_00, which is the firmware version 1.0.0-2.3.0, the others keyblob_key_source_xx do not exist in these firmware versions.

More information about the keys: "https: //gist. github. com /roblabla/d8358ab058bbe3b00614740dcba4f208" (delete spaces)


The quick solution (only for versions 1.0.0-2.3.0),

comment the following lines (366 and 367):

Code:
keyblob_key_source_id, keyblob_key_source_xx = checkfound(find_via_hashset(PKG11_data, KEY_HASHES["keyblob_key_sources"], KEY_SIZES["keyblob_key_sources"]), "keyblob_key_source_xx")
keyz[keyblob_key_source_id] = keyblob_key_source_xx

result:

Code:
#keyblob_key_source_id, keyblob_key_source_xx = checkfound(find_via_hashset(PKG11_data, KEY_HASHES["keyblob_key_sources"], KEY_SIZES["keyblob_key_sources"]), "keyblob_key_source_xx")
#keyz[keyblob_key_source_id] = keyblob_key_source_xx



Bye. :grog:

Thanks a lot man, it worked like a charm to get my 2.0.0 keys !
 

jacobfernando

Active Member
Newcomer
Joined
Jun 26, 2018
Messages
26
Trophies
0
Age
39
XP
73
Country
United Kingdom
Beware, if the script continues to give you an error, you do not have all the necessary keys in the keys.txt.


De nada :).

oye, que pena volverte a molestar me sale esto

hactool --keyset= keys.txt
Failed to read NCA header!
Invalid NCA header! Are keys correct?
Done!
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Xdqwerty @ Xdqwerty: I'm back