I thought tsec_root_key was device specific?
you're running a hactool key derivation script. none of those work on 6.2.0. that's has nothing to do with biskeydump.I was able to dump keys on 6.2 without problems. I got problems when generating keys.txt with
"Using BOOT0.bin to get keys from package1...
Could not find keyblob_mac_key_source! Please check the integrity of the data used in the current stage!" message, tho.
it is not console unique but it's not the master key, it's just an extra thing used to derive the master key since 6.2.0.No, tsec_root_key is the new name of the master_key and is the same for all the consoles.
I was using v6 when I posted thatI was able to dump keys on 6.2 without problems. I got problems when generating keys.txt with
"Using BOOT0.bin to get keys from package1...
Could not find keyblob_mac_key_source! Please check the integrity of the data used in the current stage!" message, tho.
Yes you can run biskeydump even after homebrewing. It's a payload you push just like a CFW. However, the keys aren't necessary for restoring NAND through Hekate. The keys can however check to see if your NAND backup is viable or not. Get Key 0, load rawnand.bin in HacDickMount, double click the first thing (should be something like PRODUCT or something), and put in both versions of your Key 0 and hit verify. It'll tell you if it's a usable NAND.apologies if this question is stupid.
But can I still run biskeydump even though i already homebrewed? my plan is to restore my nand but I’m not sure if the keys are needed to complete the restore.
did you get keys.txt generation working?I was using v6 when I posted that
I've heard that's common. It's probably right.Ive just dumped my Bis keys using v7, my bis_key_02 and bis_key_03 are matching. Is this correct? running 6.1
Is possible to talk in dm?if you are trying to somewhat verify a backup/rawnand via HacDiskMount, you should do that to all the partitions that take in a bis key (bis key idx mentioned in mount dialog), also the button is called Test not verify.
I also have this error, "Could not find keyblob_mac_key_source! Please check the integrity of the data used in the current stage!" How did you downgrade?I was able to dump keys on 6.2 without problems. I got problems when generating keys.txt with
"Using BOOT0.bin to get keys from package1...
Could not find keyblob_mac_key_source! Please check the integrity of the data used in the current stage!" message, tho.
No, these are hard-coded into every Switch console. The only keys that change with firmware updates are masterkeys.Does a console's SBK and TSEC key change with firmware updates?
There's switchfs, needs python 3 and fuse. It's currently read-only but that would do for getting the files out.I have MacBook Pro 2015. Any suggestion to get the files out of Rawnand file? I also have pc, but HacDiskMount can't run because of something related to 86x in pc. I know little bit of terminal stuff...