Hacking RELEASE Firmware Version Inspector - get FW version from NAND dump

[The Real Jdbye]

Have more than one NAND dump? Forgot to rename or label them?
Good news! Now you can quickly find out what firmware version a given backup contains.

Download:
Firmware Version Inspector - by shchmue on Github

Usage:
Install Python 3 and pycryptodome. In command prompt, type:

pip install pycryptodome

If this is an encrypted backup like Hekate makes (ie. you haven't dumped a decrypted System partition via HacDiskMount), you need to provide your console-specific BIS key 2. Dump this using biskeydump (https://gbatemp.net/threads/biskeyd...c-decryption-real-time-mounting-tools.502434/)

Then run from command line:

python FVI.py [-b=/path/to/biskeyfile] <dumpfile>

 biskeyfile must contain the following lines:
   BIS Key 2 (crypt): <32-digit hex key>
   BIS Key 2 (tweak): <32-digit hex key>
  omit -b if System partition already decrypted (eg. dumped with HacDiskMount)

 dumpfile must be NAND dump (eg. Hekate rawnand.bin dump) or System partition

Run examples:
View attachment 140232

View attachment 140233

I tested this on Windows 10 with Anaconda Python 3.6.5 and Ubuntu 16.04 LTS with Python 3.5.2. I hope you find it useful

This is useful, but I do have one feature request: an option to auto-rename files in a folder with serial number and firmware.

 

[Mogga666]

Support for 9.1.0?

 

[shchmue]

Support for 9.1.0?

thanks for the reminder! done.

 

[Mogga666]

thanks for the reminder! done.

Thanks for this, this tool is awesome! I was trying to figure out how to add 9.1.0 myself, may I ask how you found which .NCA it was to add into the firmware_titles.db?

 

[shchmue]

there are many ways. when a new firmware version comes out i get hactoolnet to output a list of which file name is which title ID and i end up referencing it a lot

 

[Garou]

Thanks for this, this tool is awesome! I was trying to figure out how to add 9.1.0 myself, may I ask how you found which .NCA it was to add into the firmware_titles.db?

this is the script I use to find firmware version from cart update partition, you may be able to tweak it for your own use
https://gist.github.com/garoxas/b6f2db2542250b2b34aeecc3f6fe273e

 

[SpicyMcHagis]

I am having no luck. Combed through this thread but keep getting the following message.

 

[shchmue]

I am having no luck. Combed through this thread but keep getting the following message.

no space after -b=

 

[SpicyMcHagis]

That worked!! thank you very much!!!

 

[shchmue]

9.2.0 up

 

[istovi]

I installed everything but it won't let me check the files because it cannot find FVI.py. "No such file or directory found". I looked through all the responses in this thread and can't seem to find an answer. What do I do now? I'm on Windows, thanks in advance.

 

[shchmue]

at this point since python is tricky to use for first-time users i'd recommend trying out https://gbatemp.net/threads/nx-nand-manager.533056/ nxnandmanager if possible

 

[Ottoclav]

Python and command line can be difficult for unfamiliar users, so if possible, I would recommend the wonderful NxNandManager tool, which among other things can list the firmware version of a NAND backup.

Have more than one NAND dump? Forgot to rename or label them?
Good news! Now you can quickly find out what firmware version a given backup contains.

Download:
Firmware Version Inspector - by shchmue on Github

Usage:
Install Python 3 and pycryptodome. In command prompt, type:

pip install pycryptodome

If this is an encrypted backup like Hekate makes (ie. you haven't dumped a decrypted System partition via HacDiskMount), you need to provide your console-specific BIS key 2. Dump this using biskeydump (https://gbatemp.net/threads/biskeyd...c-decryption-real-time-mounting-tools.502434/)

Then run from command line:

python FVI.py [-b=/path/to/biskeyfile] <dumpfile>

 biskeyfile must contain the following lines:
   BIS Key 2 (crypt): <32-digit hex key>
   BIS Key 2 (tweak): <32-digit hex key>
  omit -b if System partition already decrypted (eg. dumped with HacDiskMount)

 dumpfile must be NAND dump (eg. Hekate rawnand.bin dump) or System partition

Run examples:
View attachment 140232

View attachment 140233

I tested this on Windows 10 with Anaconda Python 3.6.5 and Ubuntu 16.04 LTS with Python 3.5.2. I hope you find it useful

Having an issue.

im using python 3.6.5, Windows x86 Executable from Python site. I'm not using Admin Cmd Prompt. FVI file is in a FVI folder on my desktop, and the paths for the other files are also on my desktop. I am not very savvy with cmd and terminal. Hope this is enough info to help.

 

[dza]

I dumped with biskeydump (v9) on 10.1 and tried

python FVI.py -b=biskeydump.txt rawnand.bin

Firmware Version Inspector - by shchmue
Dump is full EMMC raw NAND.
Loaded BIS keys.
Found FAT boot sector!
Scanning root for /Contents/...
/Contents/ found at cluster 0x3 address 0x148000
Scanning root for /save/...
/save/ found at cluster 0x3f01 address 0xfd40000
Scanning /save/ for System Savegame 8000000000000060...
Success! Found /save/8000000000000060.
Scanning /Contents/ for /registered/...
/registered/ found at cluster 0x5 address 0x150000
Scanning FAT for fragmentation...
/registered/ clusters:  ['0x5', '0x2be2', '0x14daa', '0x192ae']
Buffered 4 /registered/ clusters. Reading filenames...
Success! Found 197 NCA filenames.
System Version Title not found!

Does it require a 10.1 update to identify?

I was unsure if I updated to 10.1 before making a backup (though me and friend is pretty sure we did)..

I would like to verify so I am sure I can recover my nand backup safely.. Is there any risk to bricking if I attempt to restore and I remembered wrongly about updating first? Or can I simply backup again and restore that in case?

 

[shchmue]

yeah i need to update FVI for the new versions. and there’s no brick risk, if you’re on an unpatched console and you restore a backup even if there’s a fuse mismatch you can still boot CFW

 

[Buzbee]

yeah i need to update FVI for the new versions. and there’s no brick risk, if you’re on an unpatched console and you restore a backup even if there’s a fuse mismatch you can still boot CFW

Here is an updated firmware_titles.db that supports up to 10.2.0

 

[shchmue]

it’s updated to 10.2.0

 

[salitoshater]

You can also use the nx nand manager to determine the firmware version of your dump file. Just load the biskeys and the dump and that's it.

https://github.com/eliboa/NxNandManager/releases

 

[shchmue]

You can also use the nx nand manager to determine the firmware version of your dump file. Just load the biskeys and the dump and that's it.

https://github.com/eliboa/NxNandManager/releases

yes, i put that at the top of the first post a while back to encourage people to use that method