What firmware are you on? If you want to go to 6.1 you can use choidujour and just generate the new firmware and flash them
The backup which I have restored is on 6.2. What can be done?
What firmware are you on? If you want to go to 6.1 you can use choidujour and just generate the new firmware and flash them
The backup which I have restored is on 6.2. What can be done?
I'm not sure I follow.You gotta follow the guide to the t, I had to reformat my sd card to make sure the modded hekate loaded. Check the ver number.
Lockpick_RCM shows me the message: Unknown pkg1 version.
Actually yes, kind of. There were some blank boot0/boot1 dumps posted that have the personal info (at the end) removed so you can add your own. But ChoiDujour (non NX) will generate it for you so using someone elses isn't really needed, it just saves one step.Right, so can I use someone else's boot dumps?
And then decrypt it with their keys and re-crypt them again using my own console's keys?
I can't retrieve my keys in any way, though.
HacDiskMount won't allow me to open the emmc partitions, since it says both GPTs are bad.
I can't use gptrestore, as it says it won't work for memories other than 32 GB.
I'm going crazy and feeling like I'm going full circle.
You wouldn't be able to boot 6.2 OFW with 7.0 fuses (IIRC 6.2 and 7.0 have different fuse counts), but you would at least be able to boot CFW through RCM.I'm not sure I follow.
I mean, I can't boot on cfw or ofw because my boot partitions seem to be corrupted. I don't have a backup of them, only the regular 6.2 32 GB rawdump.bin file, which I have restored to the emmc (yeah, I know I lost a chunk of memory space but I've learned I can deal with it later).
Now, I can't restore the boot 0 and 1 partitions, nor dump biskeys nor fix the gpts.
Edit: Mind you, the ofw had been updated to 7.0.0 like three weeks before my emmc went kaput. Yeah, accidentally, and I deeply regret letting it happen.
Would that mean I have fuses burnt up to 7.0.0? Would that affect choidujour and the restored 6.2 nand anyhow?
I think so. The TSEC key IIRC is just a single key that's hardcoded to the console and doesn't change.Lockpick_RCM shows me the message: Unknown pkg1 version.
--------------------- MERGED ---------------------------
Also, when trying to get my TSEC keys on Hekate, it shows me this:
Unknown package1 version or reading
TSEC firmware <=´20161208142800´>.
Now, I have used another payload (biskeys) previously, which has shown me my TSEC key. Can I simply copy that key and save it as a file that would be created i Lockpick worked for me?
If you have 9 burned fuses, you need to install 7.xx firmware instead of 6.1.0.
Thanks everyone once again. Here's an update.
Due to the help of a certain guardian angel, I now have all my BISKeys, TSEC and SBK, was able to Choi my way into 6.1.0...but atmosphere or any other CFW won't boot.
It now fails to decrypt pkg2. It's puzzling, because we have double-checked everything when flashing the fw to pkg2, but still...
Rebuilding the nand is going to be the next step and attempt.
Any ideas or suggestions?