How to easy extract game files from NSP & XCI

How to easy extract game files from NSP & XCI

I made this tutorial with *.cmd file. Tools for easy unpacking files are hard to find and didn't work for me.
Tool doesn't support putting titlekey manually and never will.

My pack is good for 5 situations:
- Unpack only base game from *.NSP file
- Unpack *.NSP base game patched with *.NSP update
- Unpack only base game from *.XCI file
- Unpack *.XCI base game patched with *.NSP update
- Unpack *.XCI base game patched with *.NCA update that was already inside *.XCI

What you need is the newest as possible "keys.txt" which can be found in Google or derived from your own Switch with Lockpick tool
http://www.homebrewgeneral.net/2019/05/lockpick-switch-key-derivation-homebrew.html
http://www.homebrewgeneral.net/2019/05/switch-70-key-derivation-lockpickrcm.html
As sharing keys is illegal, it cannot be uploaded to my package.

Unpackv2.zip unlike Unpack.zip can find correct files in NSP to unpack automatically. It will crash if one NSP contains more than one game possible to launch from Home Menu.
Additionally contains countermeasures in case when there will be different quantity than 1 *.tik file (Execution aborted) or 1 *.xml file (goes to manually drop NCA file).

Download "Unpack.zip" or "Unpackv2.zip" from attachments and unpack it.
Put "keys.txt" in the same folder as "Unpack.cmd".
If your keys file is named "keys.ini" or "prod.keys", you need to rename it to "keys.txt".

Tested on Windows 10.
For best results move your game files to unpack folder.

NSP 

For Unpack.zip
1. Drop your game with *.NSP extension to "Unpack.cmd".
Wait until window will be refreshed.
In Unpack folder there is now "ExtractedNSP" folder with unpacked temporary files.

2. If you don't have update, press ENTER without writing or dropping anything and go to point 3.

2.1. Drop update file with *.NSP extension to command line.
Press ENTER.
Wait until window will be refreshed.
In Unpack folder there is now "ExtractedNSPatch" folder with unpacked temporary files.

2.2 Drop correct NCA file (probably the biggest one) from "ExtractedNSPatch" folder to command line.
Press ENTER.

3. Drop correct NCA file (probably the biggest one) from "ExtractedNSP" folder to command line.
Press ENTER.

4. Now wait until is finished. It will show you where tool unpacked game files.
If you want to delete temporary files, press two times ENTER when asked. Otherwise close window.

XCI

For Unpack.zip
1. Drop your game with *.XCI extension to "Unpack.cmd".
Wait until window will be refreshed.
In Unpack folder there is now "ExtractedXCI" folder with unpacked temporary files.

2. If you have patch with *.NSP extension, go to 2.1.1. if it's with *.NCA extension (Custom XCIs) inside ExtractedXCI, go to point 2.2.1.
If you don't have patch, press ENTER without writing or dropping anything and go to point 3.

2.1.1 Drop update file with *.NSP extension to command line. Press ENTER.
Wait until window will be refreshed.
In Unpack folder there is now "ExtractedNSPatch" folder with unpacked temporary files.

2.1.2 Drop correct NCA file (probably the biggest one) from "ExtractedNSPatch" folder to command line.
Press ENTER. Go to point 3.

2.2.1 Write "1" and press ENTER.
Drop correct NCA file (probably the second biggest file) from "ExtractedXCI" folder to command line.
Press ENTER.

3. Drop correct NCA file (probably the biggest one) from "ExtractedXCI" folder to command line.
Press ENTER.

4. Now wait until is finished. It will show you where tool unpacked game files.
If you want to delete temporary files, press two times ENTER when asked. Otherwise close window.

NSP v2

For Unpackv2.zip
1. Drop your game with *.NSP extension to "Unpack.cmd".
Wait until window will be refreshed.

2. If you don't have update, press ENTER without writing or dropping anything and go to point 3.

2.1. Drop update file with *.NSP extension to command line.
Press ENTER.

3. Now wait until is finished. It will show you where tool unpacked game files.
If you want to delete temporary files, press two times ENTER when asked. Otherwise close window.

XCI v2

For Unpackv2.zip
1. Drop your game with *.XCI extension to "Unpack.cmd".
Wait until window will be refreshed.
In Unpack folder there is now "ExtractedXCI" folder with unpacked temporary files.

2. If you have patch with *.NSP extension, go to 2.1.1. if it's with *.NCA extension (Custom XCIs) inside ExtractedXCI, go to point 2.2.1.
If you don't have patch, press ENTER without writing or dropping anything and go to point 3.

2.1.1 Drop update file with *.NSP extension to command line. Press ENTER.
Wait until window will be refreshed.
Go to point 3.

2.2.1 Write "1" and press ENTER.
Drop correct NCA file (probably the second biggest file) from "ExtractedXCI" folder to command line.
Press ENTER.

3. Drop correct NCA file (probably the biggest one) from "ExtractedXCI" folder to command line.
Press ENTER.

4. Now wait until is finished. It will show you where tool unpacked game files.
If you want to delete temporary files, press two times ENTER when asked. Otherwise close window.

Changelog:

#01.04: Pushed another version of Unpackv2 resolving conflicts with findrepl and XCI NCA Patch.
#08.04: Next Unpackv2 with fixed crashing when NSP doesn't contain XML
#10.04: Updated echos about different quantity of XML file
#11.04: Fixed unpacking XCA without patch in Unpackv2

Attached Files:

Unpack.zip
Unpackv2.zip

Post a Comment

3 Comments

  1. Learn proper language used by programer.
    Don't assume people are dumb or babies and know nothing about using those tools.
    And stop acting like you know much just from trial and error.

    When something changes, from an update, the entire guide will be outdated and outright wrong.
    Give instructions on reading instructions, don't spoon feed and give out step-by-step, you can't do that every single time, right?

    ReplyDelete
  2. This comment has been removed by the author.

    ReplyDelete
  3. I'd like to also add, your article was concise, written with a knowledge audience in mind, and was not over inflated, right to the point. Which is a perfect writing style for this kind of technical information. I hope you write more and also your change log is perfect. It tells me your article can easily be adapted when there is change and the there is not a result of your article becomming something outdated and not useful.

    PaulWilson907

    ReplyDelete