The Chevron Team is about to meet with Microsoft and they’ve put together a post with what they plan to discuss, including the importance of protecting against piracy. They also note that Chevron will be disabled with the upcoming Windows Phone 7 update. Here are their words.

As everyone is settling into the new year, we’d like to provide an update on our scheduled face-to-face meeting with Microsoft’s Windows Phone 7 team next week in Redmond.

We’ll be sharing our perspective on the homebrew potentials of Windows Phone 7 and some of the wider community feedback around the platform.

In addition to our homebrew focus, we will also be pushing for stronger protection of WP7 developer intellectual property (IP) on the platform as we believe both can co-exist on the platform.

If you have any other feedback, suggestions or even questions you feel we should bring up in our meeting, please feel free to leave a comment below.

On a similar note, we’re aware the ChevronWP7 unlocking tool is still being utilized since it has been discontinued.

Although this has been subtly communicated before, we’d like to reiterate Microsoft has informed us the “coding error” used in the ChevronWP7 unlocker will no longer work after the next Windows Phone 7 update (officially announced at CES 2011).

It will be interesting to see what the revocation of Chevron means as a possible registry tweak now exists to unlock but the method to tweak the registry relies on the Chevron method as an installer. More to come obviously…

7 COMMENTS

  1. Off-hand can you or anyone name an instance in which The Man behind the software, whether he’s behind Adobe Master Collection CS5 or he’s the man with the responsibility of doing everything he can to make some Motorola phone’s bootloader uncrackable or in this case the responsibility to make sure registries cannot be tweaked or whatever, has the man ever had success in keeping the likes of the XDA crowd down?

    While the Chevron guys may be discontinuing this, is there any certainty or even confidence that, given that there’s a strong demand to be able to tinker and that demand is shared by some really smart people, that no one else will be able to produce similar software pretty soon?

  2. And what’s up with the apparent inability of software makers, from the CSS guys in DVDs to the guys who cooked up the old payphone system that used an analog signal to advise the national provider that you’ve inserted coins which you could replicate with a $20 tone dialer and a $1 chip from Radio Shack, what’s up with the pervasive failure to secure and retain full control over such things? Is anti-piracy impossible?

Comments are closed.