yup , I got the same to ,you can unlock it again and then it is working again
Contrary to what people are saying, it doesn't look to be an MS thing. The certificate is not revoked. My guess is that the Phone checks with MS every so often to make sure that the account used to unlock it hasn't expired. Since you unlocked it in the first place by spoofing the server with your PC, it now calls home and gets told that the phone shouldn't be unlocked, and so it locks itself again. Unlocking simply resets the process.
How is that confirmation? It's just repeating the "news" that just quoted people earlier in this thread.
I suspect it's actually falling foul of a system to ensure that actual developers don't keep the device unlocked after their developer account expires, by calling back. There's no confirmation of that, admittedly, but there's not for MS remotely locking phones either, and mine makes more sense than MS suddenly pushing an OTA update to block something that's been around a good few weeks now, with no official or unofficial statement coming from anyone related to MS.
Update: It’s actually starting to look like this is a server side thing where the MS Servers check the validity of the certificate every once in a while and then automaticaly re-locks the phone if it is expired or not recognized as a valid certificate. The fact that you can re-unlock the phone afterwards means that the ChevronWP7 certificate has not been revoked yet by Microsoft.
I'm working to get approval to write about this. Contrary to reports, Microsoft is not doing anything OTA.
This would never have been an issue in the first place, if MS allowed someone to unlock their phone if they desire to do so. It should be the consumer, not MS that decides and for how long.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsPhone\ProxyPorts]“DeviceReg”=dword:000069C5