"Validate...Error!"
Closed this issue · 14 comments
When attempting to use any function of Incognito_RCM, after successfully obtaining my keys, I get this "Validate...Error!".
Switch v9.1.0 running Atmosphere 10.2
latest version is 0.6.1, not 0.5.1 @DarthAK47
latest version is 0.6.1, not 0.5.1 @DarthAK47
The picture I uploaded was accidentally chosen instead of the picture using 0.6.1.
Using 0.6.1 causes the exact same "Validate...Error!" message to appear when trying to use any function of Incognito_RCM.
@DarthAK47 I can only guess, but that means your boot0 or prodinfo are fucked, or any other part that are required to derive your SBK and TSEC keys.
@borntohonk Any idea how to fix it?
@DarthAK47 fix your own console? Only you can do that.
@borntohonk Wow, aren't you so helpful.
I was asking if whatever you said could be fixed... not can you fix it for me but OK.
@DarthAK47 i'm saying this is an issue unique to you, your setup is broken.
@DarthAK47
sorry for the late reply - can you boot into Atmosphere? And do you have a valid serial number under settings?
In the validating step the first 4 bytes of prodinfo are read and decrypted.
If those bytes do not match the "magic" identifier (CAL0) for this partition, this error shows up.
But like @borntohonk said, either key derivation failed or your prodinfo partition is corrupted (but then you shouldn't be able to boot into atmosphere).
Closing this because it seems to be unique to your setup, but feel free to comment.
@jimzrt My ns can boot into kosmos but got the same error when I try to backup or incognito. My real system version is 6.1. I tried to update the system to 8.1 or 9.0.1 or 9.1, all got the same error. Also tried emuMMC, same error too.
Btw, I'm using kosmos 15.1.
@jimzrt What's mean "first 4 bytes of prodinfo do not match the "magic" identifier (CAL0)"? How is this happen? And how may I fix this? I tried restore NAND, still not helped.
It means your prodinfo partition is hosed
Does it mean the prodinfo was broken before I backup full NAND? But I can install and run games normally. So is that a problem?
Apologies, I have opened a new bug (possibly in error) - lockpick_rcm has the same issue prior to v1.8.1 which addresses the case that PRODINFO keys are handled differently in newer consoles. The PRODINFO in this case is likely intact but behaving slightly differently to older console versions