ChevronWP7

Phone unlocks have expired :(

Hello all,

As expected, per our announcement in June, all Windows Phone developer unlocks via the Chevron Labs service expired August 11, 2012. If your phone is currently unlocked via the Chevron Labs service, your device will relock itself at next sync with the Zune desktop software. If you moved to a paid App Hub account, you may need to re-unlock the device using the Developer Registration tool.

An updated refund status post should be up tomorrow, we’re just crunching the numbers we received from Microsoft. Thanks a lot for your patience folks!

— Rafael Rivera

Where’s my App Hub refund? - Update 1

Hi all.

Just two updates:

1. Microsoft and our group have identified an issue where refunds were marked as invalid for customers that opened App Hub accounts way in the past (e.g. for forum use) but only recently purchased a subscription.
   
   Don’t worry, we will be resubmitting everyone for the next refund round. We’ll update you when that happens and when to expect your money back. I’ll make a tweak to the Where’s My App Hub Refund database to reflect this.
   
   
2. We should be receiving the results of the first refund batch in a week or so; again, will update you ASAP.

— Rafael Rivera

Where’s my App Hub refund?

As we zoom past the days in July, many of you have been wondering about the status of your App Hub refund. Let me start by apologizing for the lack of updates on this front. Ensuring Microsoft and ChevronWP7 Labs see eye to eye on disparate sets of data has been quite a challenge. Here’s where we are:

• 9551 ChevronWP7 Labs customers were submitted to Microsoft for refund processing.
   
• Only 702 of those customers came back as having a matching App Hub and ChevronWP7 Labs account.
   
• Of those accounts, 36 did not exist in a supported App Hub country and therefore were denied a refund.
   
• And of those accounts, 385 were found to have App Hub accounts opened before the January 1, 2012 date and were also denied a refund.
   
• As a result of this processing, 281 customers are in refund batch #1 and should be receiving their refunds by the end of July, if they haven’t received them already.

With these numbers in hand, we were worried that only ~3% of our customers were actually receiving refunds. After some research, we have determined there was some confusion internally and externally around the matching of ChevronWP7 and App Hub emails.

Specifically, we told our customers to ensure their Live ID matched what was in our ChevronWP7 Labs database. We discovered, however, Microsoft does not have access to App Hub Live ID information and therefore can only match based on App Hub profile information. So long story short, we screwed up.

But don’t panic! Here’s all you need to do:

1. Visit wheresmyapphubrefund.com and type in your email address. Click submit.
    
2. If the site indicates that your refund was accepted, you’re good to go! No action necessary. If not, keep reading:
    
3. Go to create.msdn.com and sign in to your account.
    
4. Click on your name in the top-right corner, then click Account Info.
    
5. Update the Email Address field on this page to match the email used at ChevronWP7 Labs. (If you need to retrieve or change the email address on file at ChevronWP7 Labs, email us.) 
    
6. You’re done! We send Microsoft a new list of eligible customers every month so check the Where’s My App Hub Refund site later to ensure your refund was processed successfully.

Again, we personally apologize for the confusion. We will continue updating the blog and the Where’s My App Hub Refund site with data as we receive it.

Thanks for your patience.

… and that’s a wrap!

As mentioned in our April announcement, ChevronWP7 Labs has been discontinued. We are now wrapping things up on our end and will be delivering, to Microsoft, a list of folks eligible for the free App Hub upgrade.

We will also be decommissioning the service website although our support email is and will remain active, in case any emergencies arise. Unlocked phones will remain unlocked until August 11, 2012.

Our support email is and will remain active, in case any emergencies arise.

Finally, all of the service’s data will be backed up for secure offline storage and completely and securely wiped from Microsoft Windows Azure servers. No external parties – including Microsoft – will have access to offline data.

Again, all of us involved - Rafael Rivera, Chris Walsh, Long Zheng and the Windows Phone team at Microsoft — are very proud to have been able to bring the ChevronWP7 Labs experiment to fruition and are excited for what the future holds.

Stay tuned!

Revision note: We mistakenly indicated that we were wiping all unlocks from our database. This isn’t actually happening until August 11. Sorry for the scare. The post has been updated to reflect this.

ChevronWP7 Labs App Hub Offer Update

Hi all. First, the team would like to apologize to everyone who has been waiting patiently for a reply to email sent in. We’re working to catch up on email.

Second, we’d like to update you on the complimentary Microsoft App Hub subscription outlined in our April 13 announcement.

To recap, customers who wish to accept the free one-year App Hub subscription must meet the following criteria:

• Have purchased an App Hub subscription between January 1, 2012 - June 12, 2012
• Have purchased at least one ChevronWP7 Labs token

To simplify the refund process and prevent any mistakes, we will deliver all eligible email addresses to Microsoft on June 13, 2012. (They will then process refunds as fast as they can, promise.) After this date, no further account changes or refunds will be possible. Please ensure that your App Hub account email address matches your ChevronWP7 Labs email address. If you’re not sure what you used or need to change your email address, email us at help@chevronwp7.com.

Thanks again for your patience.

The ChevronWP7 Labs experiment comes to an end

tl;dr The ChevronWP7 Labs service is closing. Existing customers will receive a complimentary upgrade to a Microsoft App Hub membership.

So, you may recall that ChevronWP7 Labs sold about 10,000 developer-unlock tokens in a matter of two months. Working with Microsoft over the past few months, we finished analyzing the resulting data.

The goal of this experiment was two-fold: First, to determine if we could supercharge the Windows Phone beginner/hobbyist community by removing the initial cost barrier (i.e. App Hub membership.) And second, to convert potential developers into published developers.

While we kicked butt on the former, the latter didn’t work out so well. Our data indicates that most developers simply unlocked their devices for non-developmental reasons and never went all the way to publish an app in the marketplace. There was also some confusion about the actual purpose of the ChevronWP7 service – some folks thought we provided SIM-unlock capabilities, while others thought we were a hacker group providing full root access. On top of this, there were a larger than expected number of support emails.

As a result, both sides amicably agreed to discontinue the ChevronWP7 Labs experiment.

Fear not, we will continue to explore other ideas with Microsoft. All sides are still very interested in the hobbyist and homebrew developer communities.

As a thank you gift, courtesy of Microsoft, we will be offering paid ChevronWP7 Labs users a free upgrade to a one-year membership of Windows Phone App Hub.

Users who wish to take advantage of this will need to sign up with the same Live ID as their ChevronWP7 Labs account and complete App Hub account registration with a credit card. (Your purchase will then be refunded shortly after.) More details on this below.

All of us involved - Rafael Rivera, Chris Walsh, Long Zheng and the Windows Phone team at Microsoft — are very proud to have been able to bring the ChevronWP7 Labs experiment to fruition and are excited for what the future holds.

/shout out to Brandon Watson

Upgrade offer for ChevronWP7 Labs customers: Conditions for ChevronWP7 Labs customers to receive a Microsoft App Hub Annual Membership at no cost

Microsoft is offering existing paid ChevronWP7 customers a complimentary upgrade to a Microsoft App Hub membership.

Here are the details of the offer:

1. ChevronWP7 paid customers can sign up to Microsoft App Hub for one year from supported countries or regions. (Note: Microsoft will only be able to support developers in countries or regions where payouts are supported, see list)
    
2. If a ChevronWP7 customer signs up, Microsoft will refund the first year’s registration fee via Credit Card charge reversal.
    
3. Conditions:

• ChevronWP7 customers need to register using the same email address they used to register for ChevronWP Labs service. This email address needs to be provided in the ‘personal details’ step of the App Hub registration.
• ChevronWP7 customers need to sign up within 60 days after April 13, 2012  or ChevronWP7 customers have signed up for App Hub on or after January 1^st 2012.
• Only one App Hub account per email will be refunded.

Go to the Microsoft App Hub registration page to signup: http://create.msdn.com/en-us/home/membership

FAQ

• How long does it take to receive a refund?
  All eligible refunds will be processed monthly 60 days after April 13, 2012. It may take up to 60 additional days for the refund to appear on your credit card statement.
   
• What will happen to the unlocks provided by ChevronWP7?
  Unlocks issued through the ChevronWP service will expire 120 days after April 13, 2012. If ChevronWP7 customers choose to sign up for the Microsoft App Hub membership, they will be able to re-unlock the phone after expiration.
   
• What if I’m in a country where Microsoft App Hub membership is not available?
  If you are in a country or region not covered by Microsoft App Hub (see list) there’s no possibility to take advantage of this offer at this time. However as Microsoft is adding new countries and regions regularly, ChevronWP7 customers might want to check back for expended availability to take advantage of the offer.
   
• Where can I get help if I have trouble to register?
  You can find help on the support page http://create.msdn.com/en-US/home/feedback  or for help with Registration and Account Sign In, send an email to apphub@microsoft.com

Update regarding token availability and unlock issues

Since the launch of ChevronWP7 Labs a little more than a month ago, we’ve registered and successfully unlocked nearly 5,000 phones. We’re honored to have inspired many amateur developers to begin Windows Phone development!

As you may know, we recently deactivated the sale of additional tokens. This was done to prevent an over-sell situation and to give us time to implement a new payment gateway. We’ll talk about the latter in a future post. For now, we’re sticking with PayPal.

As you read this, we’re working hard to reopen the site and resume the sale of tokens. We should be done with this in the next hour or so. Before we go live, however, we want to outline a few important changes we made to the site.

First, we added a front-facing refund policy. The policy is simple – tokens not eligible for a refund include (but aren’t limited to) those involved in retail returns, resale, warranty repair, or theft. We’ll determine final eligibility on a case-by-case basis, so don’t be afraid to ask.

Second, we changed the order in which you unlock your phone. Previously, we implied that you purchase a token prior to downloading and using the unlocker. (It was listed as Step 1 and Step 2 respectively.) We flipped these steps to ensure users try the unlock client before purchasing a token. Why?

In some cases, the client may not work correctly with your Windows Phone. An issue plaguing us since launch involves a small percentage of Windows Phone handsets not communicating with the PC properly. This issue manifests in our unlocker as the error “Unlock your Windows Phone screen to continue.” Or if you wait long enough, our tool times out and presents the “Your phone is ignoring us” message. This issue also affects the official Windows Phone Developer Registration tool, showing an error of “Unable to connect to phone. Please check that the Zune software is running […]”.

After many countless attempts to debug the issue with a plethora of Windows Phones, we regrettably concluded this is a problem beyond our control and cannot fix. We understand how frustrating this must be, especially to our early adopters. We sincerely apologize for the inconvenience. If you’re affected by this issue, here’s what you can do:

1. If you possess an HTC Arrive, try the troubleshooting steps listed in Microsoft Support KB 2537993.
    
2. Try using Windows Phone Developer Registration tool (provided as part of the Windows Phone SDK).
   
   If the tool returns an “Unable to connect to phone” message, keep reading.
   
   If you receive a message other than “Unable to connect to phone”, contact us for support. This is likely a resolvable issue that we can help with.
    
3. Try a new USB cable (particularly the cable that came with the device) and port on your PC. Remember, not all USB cables are created equal.
    
4. Reboot the phone and/or the PC.
    
5. Get in touch with Microsoft by posting in the App Hub forums, specifically the Tools For WP7 sub-forum. Be sure to state your phone cannot communicate with the PC via the official Windows Phone Developer Registration tool (see step 2) as App Hub is not a place for ChevronWP7 Labs support.
   
   NOTE: A free App Hub account is required to post on the App Hub forums. If you’re signing up on App Hub for the first time, you may be asked to become an App Hub member for $99/year. At this step, simply click the Cancel button – you will then have a free account, allowing you to participate on the App Hub (but not publish apps to the Marketplace).

We will honor any refund requests via email for users affected by this issue.

To all our users: Thanks for your patience and Happy Holidays.

- Rafael Rivera, Chris Walsh, Long Zheng

ChevronWP7 Labs Nov 14 “Mulligan” Update

Yeahhh, we’re just going to sweep that last deployment right under the rug. Sorry about that. :(

We ran into some interesting Windows Phone Support Tool binary versioning issues and also inadvertently introduced a bug in the ‘screen locked’ detection logic that blocked anyone with a developer unlocked device. (That’s pretty much everyone using the tool. Oops.)

We corrected the mistakes and pushed out a new client (0.5). Full change log follows.

Change log:

Unlock Utility

• Removed MD5 hash check of WPST binaries, as they’re not consistent across platforms
• Added load-check for old WPST binaries to replace MD5 hashing (see above)
• Broadened our WPST binary version checks, again as they’re not consistent across platforms
• Fixed a bug introduced in the “screen locked” logic, preventing unlock
• Added extra question marks to our app.config file. (Semi-inside joke.)

Web UI

• Added no-cache to IIS to help mitigate the downloading of our old broken clients.
• Added a “query parameter” at the end of our client download link to mitigate old client downloads…
• … but then removed it as Internet Explorer choked on this; it tried to save files as .5 and [1] files. (Yikes.)

Thanks for your patience!

ChevronWP7 Labs Nov 14 update

First of all, we apologize if we didn’t reply to every comment, email or Twitter message. We’re committed to ensuring the service works for everyone. Whilst a majority of users were able to unlock successfully, we’ve been working very hard to resolve some outstanding   issues for some people.

We disabled token purchasing last week to investigate some problems in the unlocking process. We had anticipated to re-enable purchasing sooner but one issue has turned out to be quite tricky.

Currently, we’re aware of an issue in which some phones do not properly communicate with the PC. This also means the unlocking process cannot be initiated. This not only affects ChevronWP7 Labs, but the official Microsoft Developer Unlock tool too.

We helped a number of users through a dozen known solutions and alternatives, all of which had no effect. Whilst some people had some success hard resetting their phone, this was neither guaranteed nor something we want to recommend.

We are currently in contact with Microsoft to explore other solutions, however this will probably take some time. Since this is an issue outside of our control, we will refund any users suffering from this problem who do not wish to wait. We ask that you first go through our support process to determine if you’re affected or not.

Needless to say, a lot of people are still waiting to use ChevronWP7 Labs. We know not being able to purchase a token has been frustrating, but please understand it was in good faith.

After implementing a number of server and client fixes today, we’re glad to announce token purchasing has now been re-enabled.

We anticipate a small number of new users will too run into the issue described above we hope they are patient while we continue our investigation.

Change log:

Unlock Utility

• Resolved an issue in which users would be taken to the unlock screen despite phone communication errors. This means if you were receiving errors before, you will now get stuck at the start of the app. until you resolve the communication issue.
• Added a Windows Phone Support Tool v2 hash check; we discovered an issue in which the tool’s Microsoft.WindowsMobile.DeviceUpdate.dll is overwritten with an older version (by either Zune or other components).
  
  
• Added a trap for uncaught exceptions, to ease the support process.

Web

• Moved FAQ to external blog post, added a link.

Backend

• Internal changes. :)

Update (15/11 10:07AM): We’ve looking into the “support tools” and “phone is ignoring us” errors with some additional information submitted by users. We hope the extra debug information will assist us in coming up with a solution.

ChevronWP7 Labs FAQ

Top questions and answers for the ChevronWP7 Labs service.

• The application stopped at “Your phone is ignoring us” (updated)
  A small number of Windows Phones have an issue communicating with the PC. This affects the developer unlocking process of both our tool and the Microsoft Developer Registration tool.
  
  We regrettably conclude this is a problem beyond our control and cannot fix. If you are affected by this issue, here’s what you can do but we cannot guarantee a successful workaround.
  
  - If you possess an HTC Arrive, try the troubleshooting steps listed in Microsoft Support KB 2537993.
  
  - Try using Windows Phone Developer Registration tool (provided as part of the Windows Phone SDK).
  
  - If the tool returns an “Unable to connect to phone” message, keep reading.
  
  - If you receive a message other than “Unable to connect to phone”, contact us for support. This is likely a resolvable issue that we can help with.
  
  - Try a new USB cable (particularly the cable that came with the device) and port on your PC. Remember, not all USB cables are created equal.
  
  - Reboot the phone and/or the PC.
  
  - Get in touch with Microsoft by posting in the App Hub forums, specifically the Tools For WP7 sub-forum. Be sure to state your phone cannot communicate with the PC via the official Windows Phone Developer Registration tool (see step 2) as App Hub is not a place for ChevronWP7 Labs support.
  
  Our refund policy (detailed below) grants users a token refund in this case. Please email us if you are affected.
  
  
• An issue occurred while unlocking
  This is in most cases a random bug. Most users have reported success after unplugging and replugging in your phone. Ensure Zune can see the device, then launch the unlock tool again. A PC reboot may help too.
  
  
• The tool asks me to install the “Windows Phone Support Tool” but it’s already installed?
  Other users who have reported this issue have reported success after uninstalling and reinstalling the Zune software
  
  
• The token appears to be “Pending” or “Used” even if unlock was unsuccessful.
  In most cases this is just to indicate the token was used in an unlocking attempt. It should work when attempting to unlock again. If it does not after multiple tries, please contact us for support.
  
  
• The phone has an “issue connecting to Microsoft server”
  The unlocking process requires the phone to communicate with Microsoft servers, if this is unsuccessful, it will not unlock. Some certain proxies may prevent this, so try at home/work if you can.
  
  1. Check your computer’s HOSTS file (C:\Windows\System32\Drivers\etc\) for a record for “developerservices.windowsphone.com”. If it exists, please remove that line.
  2. Ensure your phone’s Internet Explorer can view “https://developerservices.windowsphone.com/” (note the HTTPS). If you see an 403 error, it means it works.
  3. Toggle WiFi/3G settings and retry
     
     
• Why does the phone name need to be unique?
  The phone name (in Zune) must be unique to be registered. This is a requirement of the Microsoft registration process. It is advisable to change the name to something relatively unique (perhaps with your name) before attempting unlock.
  
  
• The tool asks me to install the “Windows Phone Support Tool” but it’s already installed?
  Other users who have reported this issue have reported success after uninstalling and reinstalling the Zune software
  
  
• Does the phone need to be plugged in during unlock queuing?
  The phone must be attached during the entire queuing process. Please do not launch Zune during this time. The application will require the screen to be unlocked (it will prompt if it is not) when the phone is ready to be unlocked.
  
  
• During the unlock process an error occurred and/or the queue appears to have frozen.
  In some circumstances the connection to the phone or internet might have been affected and will cause the unlock process to fail. In most cases restarting the app will be successful. If not after repeated attempts, please contact for support.
  
  
• What if the phone is already developer unlocked?
  Unlocking will fail if the phone is already registered to an App Hub account. To use ChevronWP7 Labs, the device must be removed from the registrar’s App Hub “devices” list.
  
  
• Why is there a queuing system?
  We implemented the queuing system in response to certain infrastructure restrictions. Although we understand it may cause delays, it is necessary to ensure the safe operation of the service. We apologize in advance for any inconveniences.
  
  
• I can’t unlock my phone. What is the token refund policy?
  The policy is simple – tokens not eligible for a refund include (but aren’t limited to) those involved in retail returns, resale, warranty repair, or theft. We’ll determine final eligibility on a case-by-case basis, so don’t be afraid to ask.