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

Search This thread

hounsell

Senior Member
Dec 25, 2009
104
27
Sleaford, UK
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...
 

Jaxbot

Inactive Recognized Developer
Mar 14, 2009
1,224
548
windowsphonehacker.com
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.
 

Darnell_Chat_TN

Senior Member
Nov 29, 2008
2,444
503
Chattanooga, TN
Google Pixel 4 XL
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.
 

hounsell

Senior Member
Dec 25, 2009
104
27
Sleaford, UK

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.
 

Darnell_Chat_TN

Senior Member
Nov 29, 2008
2,444
503
Chattanooga, TN
Google Pixel 4 XL

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.
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.
 

Darnell_Chat_TN

Senior Member
Nov 29, 2008
2,444
503
Chattanooga, TN
Google Pixel 4 XL
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.

I don't think the FCC's affirmation of consumer phone customization came with a 2 week expiration. The functionality should be built in, as Android has the setting to allow installation of apps from unknown sources, if the user so desires.
 

sadoway

Senior Member
May 28, 2008
500
136
Edmonton
can someone please tell me. in normal enlgish. hot to use TCPView to get my port cleared up... because i tried EVERYTHING else. and that has to be it.

but i dont understand it. so many numbers.
 

hounsell

Senior Member
Dec 25, 2009
104
27
Sleaford, UK
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.

This comes not from Microsoft locking out Jailbreakers, but more from the fact that ChevronWP7 uses *exactly* the same approach as a true developer unlock. It's a double-edged sword. Yes, it means that closing it is near-impossible without breaking the genuine developer unlock. On the other hand, it means it's bound to the same restrictions and checks as a true developer unlock. One of those checks is a regular callback to MS, because developer accounts can close or expire, and the phone should relock itself if that is the case. Obviously, that impacts you if your phone never was unlocked using a genuine account in the first place, but just was approved by a spoofed unlock server like how ChevronWP7 does it.
 

Mclovin1001

Member
Sep 27, 2010
47
5
Northants
Does this explain why yesturday i could unlock my phone and now i cant.

Always get the error

"Please make sure the USB is connected"
"Please restart Zune"

Or is it something different. I was able to unlock and re-lock yesturday but cant now :(
 

Top Liked Posts

  • There are no posts matching your filters.
  • 30
    As people may know, Chevron have removed their unlocker download for WP7 :( so I thought I'd archive it and make it available for everyone here still:

    http://www.megaupload.com/?d=JY0ZFVKD


    EDIT: Thanks to Cendaryn we also have the required security certificate :) - the easiest way (thanks to Talys) to install the cert and unlock your WP7 is to do as follows:

    1. Unzip file, and attach chevronwp7.cer (see below for file) to an e-mail to yourself
    2. Open email in WP7
    3. Tap attachment once, turns it into a shield, tap it again, goes to install certificate screen with white letters on black screen
    4. Click install at the bottom

    5. Make sure registry is modified:

    Code:
     [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsPhone\ProxyPorts]“DeviceReg”=dword:000069C5
    I think the WP7 developer tools from MS does this, but you can add it in manually (it's a 32bit DWORD)

    6. Plug in phone and leave Zune running
    7. Run chevronwp7.exe, click both checkboxes
    8. Click unlock

    Excellent video tutorial here thanks to Jaxbot

    [Edit 8th Dec 2010]

    Worried that Microsoft has relocked your phone? They haven't, look here

    [Edit 20th January 2011]

    Want to keep your unlocked HTC from re-locking every sync? See here

    Hope this helps someone.
    10
    Possible solution to Chevron problems.

    Hello to all!

    I think, I've finally found the reason why Chevron almost never works. After a few days of struggle, I managed to successfully unlock my HD2 three times in a row, all by the same trick.
    The idea is to change the IP which Chevron emulates DURING the process of jailbreak. Here's step-by-step.

    1 - Disable LAN card in your PC (Control Panel\Network and Internet\Network Connections\ right click on "Local Area Connection" and choose "disable"). It is very important to disable ALL connections, but you MUST remember which one is used for Internet access (see below, why).

    2 - Do all the standard steps of unlock - install certificate, start WPConnect e.t.s. When Chevron fails to unlock - LEAVE IT OPEN.

    3. Start Notepad and open hosts. Delete lines added by Chevron (at the bottom). Save. LEAVE NOTEPAD OPEN.

    4. Press Win+R and enter IPConfig /flushdns , press "enter". CMD window will blink for a second - that's normal.

    5. Press Win+R again (there will be IPConfig /flushdns typed already), but DO NOT PRESS "ENTER", just leave this window open.

    6. Now the trick. Start WPConnect. WHILE it connects, continue to repeatedly press "Unlock" button in Chevron, until the black CMD window of WPconnect disappears. Chevron will fail to do its job, but that's in fact is the very thing we need.

    7. Now, do not touch Chevron window, just return to Network Connections and ENABLE yor LAN card.

    8. Go to Notepad and JUST CLICK "Save", do not alter anything inside.

    9. Return to the window with the typed command IPConfig /flushdns . Press Enter.

    10. Start WPConnect, WAIT until it disappears, and press "Unlock" button in Chevron. You're done - this time unlock would work.

    At least, it worked for me 3 times in a row, while NO other ways worked.

    Best regards - Draco.

    P.S. If you have firewall - disable it before doing anything.

    P.P.S. Win7 from NAND + MDJ Desire HD 4.4 from SD = best phone in the world :)
    7
    so who saved the .cert on his pc ?

    aaahm.... I guess I have something for you :)
    6
    Succeeded

    Okay so here is *everything* I did to succeed in re-unlocking my Samsung Focus

    1. Have Winphone developer tools installed
    2. Connect Phone via USB
    3. Wait till zune starts and sync completes
    4. Verify that zune is not in a guest relationship
    5. open a command prompt, type netstat -a to confirm that port 443 is not being used
    6. open an admin command prompt, navigate to c:\windows\system32\drivers\etc\ then type notepad hosts and delete any references to windowsphone developer services
    7. go to the settings on the phone and turn airplane mode on (so that the phone is forced to use internet via zune)
    8. While the phone is still on the settings page, run Chevron with admin privileges

    And it worked!
    5
    If you are having issues, you should also make sure that your machine isn't running anything that may be using port 443 (including IIS, Skype, etc)