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

  • Thread starter Thread starter shchmue
  • Start date Start date
  • Views Views 46,345
  • Replies Replies 119
  • Likes Likes 38
That did help it seems, however now I'm getting this error.
View attachment 149990
is your python3 64 bit maybe? this might require 32-bit
The error I always get is:
View attachment 150107

I tried so many different variations for the paths. With slash, with backslash, with "/c/", with "C:\\", copying the files in different directories, copying everything in the same one and use the file names directly instead of paths.
sounds like you're running this in python2. install python 3 32-bit and try again
 
okay Imanaged to get it working with my 6.0.1 nand backup but with 6.1.0 it gave "System Version Title not found!" :huh:
 
So im getting this error on my mac just running 'python FVI.py'
File "FVI.py", line 108 def find_record_by_filename(buffer, name: bytes):
(^ under : in name: bytes)
SyntaxError: invalid syntax

any help? Im using the latest python 3.7 and redownloaded the latest pycryptodome
 
Last edited by lovebirdlover,
So im getting this error on my mac just running 'python FVI.py'
File "FVI.py", line 108 def find_record_by_filename(buffer, name: bytes):
(^ under : in name: bytes)
SyntaxError: invalid syntax

any help? Im using the latest python 3.7 and redownloaded the latest pycryptodome
you're positive you're running this on Python 3 and not 2? can you send a complete screenshot of the terminal when it errors? feel free to censor names and keys
 
you're positive you're running this on Python 3 and not 2?

I'd say they're running it on 2... on my mac, when I installed Python using Brew, I got both 2 and 3, and I have to explicitly use "python3" and not just "python" as they did here:

on my mac just running 'python FVI.py'

See:
a.png
 
  • Like
Reactions: shchmue
you're positive you're running this on Python 3 and not 2? can you send a complete screenshot of the terminal when it errors? feel free to censor names and keys

Okay so i solved this error but im getting a new one which another user was having above. I had to copy the Crypto folder from my python directory into FVI-master and got this new one.
 

Attachments

  • Capture.PNG
    Capture.PNG
    4 KB · Views: 145
Hey just posting for posterity, I got the "contents not found" error a user had above and it was because I had no idea what was meant by "tweak" and "crypt" BIS keys, because my biskeydump version just gave me a single long hex number for BIS key 2. I couldn't find any info on this anywhere so I used an older biskeydump version, and it turns out that the long, 64 bit hex number was actually both combined. I took the first 32 bit half and put it as BIS Key 2 (crypt), and the second 32 bit half and made it BIS Key 2 (tweak). It then worked fine. (Looks like the contents not found error is just when the bis keys are wrong?)

Anyway this is probably a really silly roadblock to have but hopefully this could help any frustrated newbies like me!! Very helpful program, thank you.
 
  • Like
Reactions: hippy dave
Hey guys I am trying to use this program to check the firmware on my backup. However, I keep getting this error. I also tried it, wrapping the Bis Keys numbers <XXXXXXXX> it still did not work, btw that is the only two lines in the biskeys's folder. Any ideas?

upload_2018-12-11_16-14-35.png


upload_2018-12-11_16-16-42.png
 

Attachments

  • upload_2018-12-11_16-13-51.png
    upload_2018-12-11_16-13-51.png
    21 KB · Views: 218
Hey guys I am trying to use this program to check the firmware on my backup. However, I keep getting this error. I also tried it, wrapping the Bis Keys numbers <XXXXXXXX> it still did not work, btw that is the only two lines in the biskeys's folder. Any ideas?

View attachment 151743

View attachment 151744
remove the spaces before each line, those are only in the info text so that it looks nice :x
 
Thank you! it works like a charm!.....now i will create another post to see if there is a way to restore a dead switch... lol. But thanks again. its a 6.2.0 backup.. which I restored, but didn't have the boot0 or boot1.
 
Thank you! it works like a charm!.....now i will create another post to see if there is a way to restore a dead switch... lol. But thanks again. its a 6.2.0 backup.. which I restored, but didn't have the boot0 or boot1.
for that you'll need to either do an entire ChoiDujour procedure to any firmware below 6.2.0 (it doesn't support that target yet) or make one of the same firmware version that's in your boot0 and skip flashing boot0/1
 
  • Like
Reactions: tremendazo
So im getting a new error regarding my BIS keys. I had double checked and confirmed its the right one by doing a backup twice. Whats wrong?

EDIT: NVM SOLVED! Forgot to put -b flag
 

Attachments

  • Capture.PNG
    Capture.PNG
    3.2 KB · Views: 223
  • k.PNG
    k.PNG
    3.9 KB · Views: 177
Last edited by lovebirdlover,
for that you'll need to either do an entire ChoiDujour procedure to any firmware below 6.2.0 (it doesn't support that target yet) or make one of the same firmware version that's in your boot0 and skip flashing boot0/1

Hey just wanted to say thank you. I was able to downgrade back to 4.1 using my biskeys, ChoiDujour and a keys.txt file that is flying around the internet...Cough Max... Cough site. Now i just have to figure out, hot to boot with 8 burn fuses. all I'm getting is nintendo logo and black screen.
 
Hey just wanted to say thank you. I was able to downgrade back to 4.1 using my biskeys, ChoiDujour and a keys.txt file that is flying around the internet...Cough Max... Cough site. Now i just have to figure out, hot to boot with 8 burn fuses. all I'm getting is nintendo logo and black screen.
it doesn't boot even with CFW?
 
Can someone tell me what's wrong and what i'm missing? I've done all I can to try to figure Python on but, man i'm just lost :wacko: Trying to fix my switch but, don't remember what firmware version was on this when I backed it up.
 

Attachments

  • FVI.jpg
    FVI.jpg
    136.9 KB · Views: 158

Site & Scene News

Popular threads in this forum