FORUMS

Xposed 3.0 Alpha 3 Released

A new alpha for the Xposed framework is out and brings several bug fixes. You’ll only need to flash … more

XDA Recap: This Week In Android (Apr 18 – 25)

Here in the digital XDA newsroom, we spend our days pouring over an average of … more

Sunday Debate: Custom ROMs vs. Modular Tweaks

Join us in a fun Sunday Debate on Mods and ROMs. Come with your opinions and feel free to … more

AOSP 5.1 Lollipop for Nexus Q

Google Nexus Q is an intriguing device released with Android 4.0 Ice Cream Sandwich. It was abandoned by … more
Post Reply Subscribe to Thread Email Thread

ChevronWP7 Unlocker & Cert download - *here* + video tutorial

7th December 2010, 07:13 PM |#101  
ceesheim's Avatar
Forum Moderator
Flag No Android Fanboys Please !!!
Thanks Meter: 2,227
 
Donate to Me
More
yup , I got the same to ,you can unlock it again and then it is working again
 
 
7th December 2010, 08:25 PM |#102  
Junior Member
Flag Vienna
Thanks Meter: 2
 
More
Quote:
Originally Posted by ceesheim

yup , I got the same to ,you can unlock it again and then it is working again

yeah, but how long...
7th December 2010, 08:25 PM |#103  
Recognized Developer
Thanks Meter: 548
 
Donate to Me
More
Quote:
Originally Posted by mathiaspe

yeah, but how long...

Unlocked my device around 2:40ish, and it's already relocked for the second time. Not looking good, folks.
7th December 2010, 08:27 PM |#104  
Senior Member
Flag Sleaford, UK
Thanks Meter: 27
 
More
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.

That's my guess anyway. Rafael tweeted to say it wasn't an MS thing either, and that there'd be a blog post coming to explain it...
7th December 2010, 08:28 PM |#105  
Recognized Developer
Thanks Meter: 548
 
Donate to Me
More
Quote:
Originally Posted by hounsell

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.

I agree. If Microsoft was really trying to destroy homebrew, they would've said something by now. And would've blocked ChevronWP7 entirely.
7th December 2010, 08:36 PM |#106  
Senior Member
Thanks Meter: 28
 
More
confirmation here => http://windowsphonehacker.com/micros...7-12-07-10.php
7th December 2010, 08:50 PM |#107  
Darnell_Chat_TN's Avatar
Senior Member
Flag Chattanooga, TN
Thanks Meter: 410
 
More
Thumbs down
Does not matter whether MS put it in place before the device was sold or initiated it after the sale. Bottom line is that MS via WP7 is not allowing customers to express the FCC (USA) affirmed ability to customize their own property.
7th December 2010, 09:01 PM |#108  
Senior Member
Flag Sleaford, UK
Thanks Meter: 27
 
More
Quote:
Originally Posted by hd2leo_fusion

confirmation here => http://windowsphonehacker.com/micros...7-12-07-10.php

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.
7th December 2010, 09:07 PM |#109  
gcmobile's Avatar
Junior Member
Flag Cologne
Thanks Meter: 0
 
More
It runs fine here - no probs - no message - no lock

Regards
gc
7th December 2010, 09:11 PM |#110  
Darnell_Chat_TN's Avatar
Senior Member
Flag Chattanooga, TN
Thanks Meter: 410
 
More
Quote:
Originally Posted by hd2leo_fusion

confirmation here => http://windowsphonehacker.com/micros...7-12-07-10.php

Quote:
Originally Posted by hounsell

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.

The article that link cites as its source of their post has already updated their thread to mention it's likely not an OTA kill directed at the app.
Quote:

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.

My whole issue, is that even the FCC has affirmed anyone can customize their own phone, which is their personal private property. And MS has made it very hard for a consumer to do so. I'm just not a fan of these built in measures that twart a consumer from expressing a little freedom with phones they purchase.
Post Reply Subscribe to Thread

Tags
chevron, unlock
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes