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

  • Thread starter Thread starter shchmue
  • Start date Start date
  • Views Views 46,726
  • Replies Replies 119
  • Likes Likes 38
finally got this to run (my syntax understanding is awful), but now I get the error /contents/ not found.

This is a dump from I believe 5.0, but I wanted to check before I restore.

Any thoughts?

Thanks in advance for the help.
that's pretty weird. that means it successfully decrypts so the bis keys are correct, it just can't find /contents/ in the partition table. if you can use memloader + hacdiskmount to mount your system partition and post the results of running the command DIR inside the system:/contents/registered folder (put it inside a QUOTE block on the forum please) then i can tell you which firmware it's from
hmmm maybe making new nand backups might be easier lol.
yeah, what drax said or just use this tool and try bis keys until one works are the only practical ways to do it
 
Last edited by shchmue,
what happens when you type the command i wrote

upload_2018-11-21_12-45-18.png


I have a feeling I'm doing it wrong...
 
Ok getting closer...still need help though. I'm pretty sure I have input the directory structure correctly, but it's not recognizing the dump file.



For the text within the biskeydump.txt file, can I just copy/paste the text that was generated by the QR code?
 
Last edited by Shoruk3n,
Ok getting closer...still need help though. I'm pretty sure I have input the directory structure correctly, but it's not recognizing the dump file.

View attachment 149938

For the text within the biskeydump.txt file, can I just copy/paste the text that was generated by the QR code?
oh! i guess mine takes linux style paths because of stuff i have installed. instead of typing the paths like the example, just drag each file onto the command prompt and it’ll produce a compatible path with c:\ instead of /c/. not sure about the QR code, it never worked for me i just did the method from the biskeydump readme where it dumps the output into command prompt and i copied it into a text file
 
Drag/drop works great!

Would you mind copy/paste the contents of your biskeydump.txt (without the actual keys of course)? This is where I am now...

View attachment 149956
you missed the -b= before the biskeydump file path but as it says in OP it needs these two lines
Code:
BIS Key 2 (crypt): <32-digit hex key>
BIS Key 2 (tweak): <32-digit hex key>
 
you missed the -b= before the biskeydump file path but as it says in OP it needs these two lines
Code:
BIS Key 2 (crypt): <32-digit hex key>
BIS Key 2 (tweak): <32-digit hex key>

That was it! I missed the -b.

upload_2018-11-21_17-8-53.png


My console is still on 5.1.0, so there shouldn't be any issues with restoring with this dump right?
 
I've been having some issues as well. I've installed Python 3 (made sure to completely remove my previous install of python 2) Used pip to install cryptodome but I keep getting this error and Im not exactly sure why.
test.PNG
 
Thanks! That was exactly what I was looking for. Did a backup from my wifes console when I bought it a few months ago but I forgot to look for the version and upgraded it afterwards.
Yesterday I guessed the version by serial number and today I could confirm it :)

BTW: If you never booted the console and made a backup, the date will be a zero value:

Most recent boot: 1980-01-01 00:00:00
 
The error I always get is:
upload_2018-11-24_14-26-31.png


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.
 

Attachments

  • upload_2018-11-24_14-26-3.png
    upload_2018-11-24_14-26-3.png
    2.5 KB · Views: 188

Site & Scene News

Popular threads in this forum