Feeds

Microsoft gives Phone 7 Mango jailbreak its blessing

If it's good enough for ChevronWP7, it’s good enough for hobbyists

Providing a secure and efficient Helpdesk

Microsoft has shifted its stance on the jailbreaking of its Phone 7 operating system, and seems to be embracing – rather than trying to crush – such developments.

Redmond has had an ongoing feud with the developers at ChevronWP7 ever since the group put out a jailbreak for Phone 7 a year ago, allowing users to run applications that haven’t been signed off by Microsoft. Phone 7 users can do this anyway by paying Redmond $99 a year for the developer program, but ChevronWP7 offered the ability for just $9 per handset.

Last December, Microsoft blocked unlocked handsets from receiving updates, but said it wouldn't brick them. In May of this year, Phone 7 director Brandon Watson said: “Unfortunately for those customers out there who acted on information from sources outside of Microsoft, the rubber meets the road today.” But the exact relationship between said rubber and said road remained somewhat murky.

But Microsoft now appears to be changing its tune. The latest version of the ChevronWP7 code, released this weekend, has Microsoft’s blessing, and requires a Windows ID to use. The price remains the same, and it looks as though Microsoft will support the code.

“Microsoft is collaborating with the ChevronWP7 team in its efforts to create tools for the Windows Phone hobbyist developer community,” Redmond told The Register in a statement. “We are working with ChevronWP7 team to help ensure that their tools are safe for hobbyist developers while respecting the intellectual property of our developer community. Microsoft believes in enabling as many developers and enthusiasts as possible, empowering them to learn, grow, and get the most benefit on our platform.”

From the text of the statement it looks very likely that Redmond is changing its thinking on the subject of jailbreaking. This could be no bad thing, given that it’s looking to get the maximum number of developers working on the mobile operating system, and it will please many in that community. ®

Security for virtualized datacentres

More from The Register

next story
TEEN RAMPAGE: Kids in iPhone 6 'Will it bend' YouTube 'prank'
iPhones bent in Norwich? As if the place wasn't weird enough
Consumers agree to give up first-born child for free Wi-Fi – survey
This Herod network's ace – but crap reception in bullrushes
Crouching tiger, FAST ASLEEP dragon: Smugglers can't shift iPhone 6s
China's grey market reports 'sluggish' sales of Apple mobe
Sea-Me-We 5 construction starts
New sub cable to go live 2016
New EU digi-commish struggles with concepts of net neutrality
Oettinger all about the infrastructure – but not big on substance
PEAK IPV4? Global IPv6 traffic is growing, DDoS dying, says Akamai
First time the cache network has seen drop in use of 32-bit-wide IP addresses
EE coughs to BROKEN data usage metrics BLUNDER that short-changes customers
Carrier apologises for 'inflated' measurements cockup
Comcast: Help, help, FCC. Netflix and pals are EXTORTIONISTS
The others guys are being mean so therefore ... monopoly all good, yeah?
prev story

Whitepapers

Forging a new future with identity relationship management
Learn about ForgeRock's next generation IRM platform and how it is designed to empower CEOS's and enterprises to engage with consumers.
Storage capacity and performance optimization at Mizuno USA
Mizuno USA turn to Tegile storage technology to solve both their SAN and backup issues.
The next step in data security
With recent increased privacy concerns and computers becoming more powerful, the chance of hackers being able to crack smaller-sized RSA keys increases.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.
A strategic approach to identity relationship management
ForgeRock commissioned Forrester to evaluate companies’ IAM practices and requirements when it comes to customer-facing scenarios versus employee-facing ones.