Homebrew RELEASE NxFileViewer

[MysterTee]

Welcome to the official NxFileViewer thread

NxFileViewer allows you explore the content of your Nintendo Switch files.

Features

• Based on LibHac
• Supported files: NSP, NSZ, XCI, XCZ
• Supports Super NSP/XCI
• Browse files content structure
• Export files
• Save or copy title images
• Specify your own keys location
• Searches keys in commonly used locations
• Automatically download keys from an URL defined in the settings
• Supports drag and drop
• Checks real files type (XCI or NSP)
• Detailed log
• User-friendly and responsive interface
• Single executable file
• Do not write anything outside of the program directory
• Verify hash and signature
• Displays missing keys
• Opens title URL
• Multiple languages (actually English and French, PR me for more )
• Advanced files renaming

Download

https://github.com/Myster-Tee/NxFileViewer/releases

Screenshots

Spoiler

Changelog
v2.7.0

• Based on LibHac v0.19.0
• Do not anymore try to open sparse sections to avoid reporting unexpected errors
• Notification displayed when no prod.keys is found
• NcaSectionType property added to Section in structure tree
• Updated to .NET 7

Spoiler: Old Changelog

v2.6.1

• Fix duplicated files display (in structure view) for file system sections (issue #5)
• Fix wrong error reporting for titles with Brazilian/Portuguese icons

v2.6.0

• Based on latest LibHac release (v0.16.0)
• Possibility to rename files with custom options
• Fix «Offset must be a multiple of 16» when opening update files
• Settings can be reset to default
• Many small improvements

v2.5.0

• Based on latest LibHac release (v0.15.0)
• Possibility to open a Web page for the loaded title (based on the Title ID)
• Possibility to save decrypted NCAs
• NCA hash strategy changed, now based on CNMT metadata file
• Property «IsNCA0» added for NCA
• French language supported (language can be changed in the settings)
• Some small issues fixed
• Based on .NET 6

v2.4.0

• Properties of ticket files (*.tik) are displayed
• Title ID keys from the ticket files are now loaded and used for opening NCA contents

v2.3.0

• Keys files being used are displayed in the settings
• New command added for reload keys on demand
• «title.keys» can also be downloaded from an URL defined in the settings
• Can edit keys from the settings
• New setting added for reloading keys each time a file is opened
• Keys download URL can be immediately tried
• Missing title keys are displayed via an icon in the status bar
• Can open location of opened file via context menu of «Overview» tab
• NCA (or NCZ) Sections are displayed even when content can't be opened
• FIX: NCA hash is not anymore considered valid when NCA content cannot be opened
• Hash status moved to «Section» items instead of «NCA» items
• Tooltip added for displaying NCA's hash or NCA's signature error
• Text of help tooltips can be copied

v2.2.0

• Hash of NCAs can now be verified
• Header signature of NCAs can now be verified
• Long time actions are now threaded (a status bar and a progress bar have been added )
• Possibility to save a Directory (was not finished in previous version)
• Possibility to save a NCA Section
• Possibility to save a PartitionFileEntry
• Program can now open supported files at startup when program is associated with supported files
• Errors are marked on the corresponding structure tree item when applicable
• Item's errors can be opened in a specific window
• Displayed item's properties order improved
• Size of PartitionFileEntry displayed
• Lazy loading option removed (as file opening is now threaded, it is better to always reveal possible errors)
• Fix initial directory when browsing for a file to open
• Lots of small UI changes and improvements

v2.1.0

• New setting added to select the structure tree loading mode
• Fix a display bug in the settings when cancel button was clicked
• Enum settings are now saved as string instead of integer (better readbility)
• Change version format in overview tab (displayed as 65536, 131072, etc instead of 0.1.0.0, 0.2.0.0)
• Opened file logged
• Log level can be selected in the settings
• Keys download URL can be defined in the settings
• The ModuleID (also known as Build ID) is displayed in the properties when the «main» program file is selected (requested by BigOnYa)
• Some extra properties added to display
• Missing NCAs of type «DeltaFragment» are logged as warning instead of error (maybe normal ?)

v2.0.0

• Now based on LibHac (hactool not anymore required)
• In addition to NSP, now supports NSZ, XCI and XCZ
• Supports Super NSP/XCI
• Full file content structure browsing
• Export contained files
• Save or copy title images
• Specify your own keys location
• Searches keys in commonly used locations
• Automatically download keys from an URL defined in the settings
• Supports drag and drop
• Checks real files type (XCI or NSP)
• Nearly totally redevelopped
• Now based on .NET 5
• Prepared for beeing translated in other languages

v1.0.0

• Initial release

 

[hippy dave]

I was looking at this today, it's good
Suggestion - you could display the titlekey that's contained within the *.tik file of an .nsp

 

[MysterTee]

I was looking at this today, it's good
Suggestion - you could display the titlekey that's contained within the *.tik file of an .nsp

Thank's, I'll think of it.

 

[Kino101]

Great, I'll try it soon

 

[BigOnYa]

I love this. It even lists the Build ID. Awesomeness!

 

[MysterTee]

I was looking at this today, it's good
Suggestion - you could display the titlekey that's contained within the *.tik file of an .nsp

This is now implemented in version 2.4.0

 

[hippy dave]

This is now implemented in version 2.4.0

Great job!

 

[Fadi5555]

That’s amazing

 

[MysterTee]

Hey there!

I just release a new version of NxFileViewer with a new cool feature for renaming your package files

 

[Kino101]

Nice renaming feature! Thanks.

 

[MysterTee]

v2.6.1 released.

 

[Youffie]

cannot open the app, every time it ask me to install .net framework, I repair it with installer, restart computer and still ask me to install it . . .

 

[MASSI]

thank you very muck

but i small problem with your software, i can't see the information of my file

thanks by advance for the help

 

[linga]

https://github.com/Myster-Tee/NxFileViewer/issues/8
Hi, I'm having issues extracting the update patch with it, can this be fixed?

 

[veggav]

I'm having a very small problem that I would like to fix for consistency with all my other files.

NxFileViewer output a different version for updates and dlcs compared to other content found around.
Example:

MustacheMan Car 8 Deluxe [TitleID] [v786432].nsz is the most common filename I see.
NxFileViewer renames to MustacheMan Car 8 Deluxe [TitleID] [v12].nsz

Why is that? Is it possible to have the same renaming scheme?

EDIT: Nevermind, just have to change the pattern to {VerNum}

 

[ake7440]

thank you very muck

but i small problem with your software, i can't see the information of my file

thanks by advance for the helpView attachment 308665

I also have the same problem. Could you fix it now?

Edit ******** I can fix it now **********

you just need to put the file prod.keys & title.keys into the same folder of NxFileViewer.

You just need to search these files from google. It's the same file that use for Emulators.

 

[DARKFiB3R]

I love this. It even lists the Build ID. Awesomeness!

Where are Build IDs listed?

Edit:

v2.1.0 2021/01/30
The ModuleID (also known as Build ID) is displayed in the properties when the «main» program file is selected (requested by BigOnYa).

NxFileViewer > Content > blahblah.nsp > xxxxxxxxx.nca (Program) > Section 0 > Main > ModuleId:

The first 16 digits of ModuleId is the Build ID

----------------------------

Edit 2:

I'm confused again lol.

I have an .xci file that has a shit ton of xxxxxxxxx.nca (Program)

---------------------------

Edit 3:

I haven't been able to locate the Build ID displayed by Edizon in that .xci, but I have found a known build ID but but it's in a different location.

NxFileViewer > Content > blahblah.xci > Secure > xxxxxxxxxxxxxxxxxxxx.nca (Program) > Section 0 > main > ModuleId: FE1B230800D4933C617C691273CA597800000000000000000000000000000000

Can anyone help me understand this stuff? Thanks.

 

[RedColoredStars]

There is a section in the app to put console.keys. What is this file and how do I get it? I've not seen it mentioned in any guides at all. Is it even necessary to use? The follow errors occur but the program too to work fine otherwise.

«console.keys» file used: [none]
Failed to match key device_key_4x
Failed to match key eticket_rsa_kek_source
Failed to match key eticket_rsa_kekek_source
Failed to match key save_mac_key
Failed to match key ssl_rsa_kek_source
Failed to match key ssl_rsa_kekek_source
Failed to match key ssl_rsa_key

Even if I should just ignore the erros, I'd still like to know what the file is and how to get it.

 

[BigOnYa]

There is a section in the app to put console.keys. What is this file and how do I get it? I've not seen it mentioned in any guides at all. Is it even necessary to use? The follow errors occur but the program too to work fine otherwise.

«console.keys» file used: [none]
Failed to match key device_key_4x
Failed to match key eticket_rsa_kek_source
Failed to match key eticket_rsa_kekek_source
Failed to match key save_mac_key
Failed to match key ssl_rsa_kek_source
Failed to match key ssl_rsa_kekek_source
Failed to match key ssl_rsa_key

Even if I should just ignore the erros, I'd still like to know what the file is and how to get it.

Every Switch console has it's own unique set of keys = (keys.txt/prod.keys). You can either 1- Find and download somebody elses Keys from the internet and use, or 2 - Use a tool called PickLock (formally called LockPick) and get your own personal Keys from your switch. https://gbatemp.net/threads/lockpick_rcm-payload-official-thread.532916/post-10266016

Post automatically merged: Dec 15, 2023

Where are Build IDs listed?

Edit:



NxFileViewer > Content > blahblah.nsp > xxxxxxxxx.nca (Program) > Section 0 > Main > ModuleId:

The first 16 digits of ModuleId is the Build ID

----------------------------

Edit 2:

I'm confused again lol.

I have an .xci file that has a shit ton of xxxxxxxxx.nca (Program)

---------------------------

Edit 3:

I haven't been able to locate the Build ID displayed by Edizon in that .xci, but I have found a known build ID but but it's in a different location.

NxFileViewer > Content > blahblah.xci > Secure > xxxxxxxxxxxxxxxxxxxx.nca (Program) > Section 0 > main > ModuleId: FE1B230800D4933C617C691273CA597800000000000000000000000000000000

Can anyone help me understand this stuff? Thanks.

The first 16 digits of this number/letters is your Build ID. It is FE1B230800D4933C

 

[RedColoredStars]

Every Switch console has it's own unique set of keys = (keys.txt/prod.keys). You can either 1- Find and download somebody elses Keys from the internet and use, or 2 - Use a tool called PickLock (formally called LockPick) and get your own personal Keys from your switch. https://gbatemp.net/threads/lockpick_rcm-payload-official-thread.532916/post-10266016

I already tried that and also this one before posting:
https://vps.suchmeme.nl/git/mudkip/Lockpick_RCM/releases

They both only put out a dev.keys, prod.keys, and title.keys file. Trying to use any of those in NxFileViewer's "console.keys" section just results in errors. So I will ask again, how is the correct file to use with this app obtained? Even if it doesn't matter whatsoever. It's more of a learning thing for me. I just like to know.