HTC Explains Android Bootloader Unlock Process, Warranty-Voiding Tool - EVO 4G General

HTC Explains Android Bootloader Unlock Process, Warranty-Voiding Tool Coming Later This Month
It’s been a few months now since HTC CEO Peter Chou announced that the company will no longer be locking bootloaders on their devices, and enthusiasts have had nothing to show for it. Many of HTC’s recent devices are still locked up tight, prompting many to wonder when they would deliver on their promise. Thanks to an updated Facebook post and a well-timed tweet, though, we now have the answers we’ve been waiting for.
The process will begin with a web tool (due out later this month) through which you register an account and waive all liability in the event things go horribly wrong. That’s right folks, since unlocking the bootloader gives you a much greater level of control over how the device operates, you can kiss parts (or all) of your warranty goodbye. Once that’s done, you connect the Android device in question to computer with the SDK installed, and you’ll receive a “device identifier token” which gets plugged into the web tool to generate a unique unlock code.
Sounds simple enough, right? The first devices that are set to benefit from the unlocking treatment are the global version of the HTC Sensation, followed buy T-Mobile’s version of the device and the Sprint Evo 3D. Since unlocking the bootloader is one the of the first steps to running a custom ROM and really having some fun with your Android device, it’s heartening to see them focus on getting newer hardware opened up. Hopefully the floodgates will soon open, and we can start messing with our HTC toys with reckless abandon.
here is a section i took from their facebook post
Update on Bootloaders
by HTC on Tuesday, May 24, 2011 at 4:50pm
Thanks so much for providing feedback, we hear your concerns. Your satisfaction is a top priority for us and we're working hard to ensure you have great experiences with our phones. We're reviewing the issue and our policy around bootloaders and will provide more information soon. Thank you for your interest, support and willingness to share your feedback.
**UPDATE**
We’ve listened. Check out the statement from our CEO, Peter Chou on HTC bootloaders. Click the link for more info.
**UPDATE 7/10**
We wanted to provide an update on HTC’s progress with bringing bootloader unlocking to our newest phones. We know how excited some of you are for this capability, and we’ve put significant resources behind making this change as soon as possible. While we wish we could flip a simple switch and unlock all bootloaders across our device portfolio, this is actually a complex challenge that requires a new software build and extensive testing to deliver the best possible customer experience.
We’re thrilled to announce today that software updates to support bootloader unlocking will begin rolling out in August for the global HTC Sensation, followed by the HTC Sensation 4G on T-Mobile USA and the HTC EVO 3D on Sprint. We’re in the testing phase for the unlocking capability now, and we expect it to be fully operational by early September for devices that have received the software updates. We'll continue rolling out the unlocking capability over time to other devices as part of maintenance releases and new shipments.
HTC continues its commitment to unlocking bootloaders and supporting the developer community. Because of the importance of this community to us, please expect an update on this about every few weeks as we make progress toward launch. Thank you for your patience and continued support!
**UPDATE 8/3/2011**
Since our last update, many of you have asked how the bootloader unlocking process will actually work, and in particular why HTC's most recently released devices still have a locked bootloader. Rest assured we're making progress toward our goal to roll out the first software updates in August to support unlocking for the global HTC Sensation, followed soon by the HTC Sensation 4G on T-Mobile and the HTC EVO 3D on Sprint. Because unlocking the bootloader provides extensive control over the device and modifications may cause operation, security and experience issues, new devices will continue to ship locked but will support user-initiated unlocking using a new Web-based tool.
So how will this work? The Web tool, which will launch this month, requires that you register an account with a valid e-mail address and accept legal disclaimers that unlocking may void all or parts of your warranty. Then plug in your phone to a computer with the Android SDK loaded to retrieve a device identifier token, which you can then enter into the Web tool to receive a unique unlock key via e-mail. Finally, apply the key to your device and unlocking will be initiated on your phone.
We're excited to bring bootloader unlocking to developers and enthusiasts, and we feel this new Web tool will meet your needs and continue to provide customers with the best experience. Thanks to the community for supporting these efforts!

http://forum.xda-developers.com/showthread.php?t=1201270

Related

Any OFFICIAL source for a bootloader-unlocked phone?

I noticed that Google is now selling Nexus Ones through the developer channel to registered developers, but this appears to be a bootloader-locked retail device, not any type of engineering device. They also sell what appears to be an ION, also bootloader-locked.
So while this is fine for testing your apps, there appears to be no legitimate/officially sanctioned way for an individual developer to get a phone on which he/she can test alternate builds of Android itself.
Of course, anyone familiar with this forum knows how easy it is to root these devices, and of course with the Nexus One in particular you can unlock the bootloader yourself, but it seems strange that Google makes no provisions for allowing developers to work on Android itself on real hardware. They make Android open source but then provide no official way to try your builds on an actual device.
I guess "real" engineering bootloader-unlocked devices are only made available to "real" partners (cell phone providers, hardware manufacturers, etc.).
You can unlock bootloader Yourself in N1.

[NEWS] Microsoft to officially support homebrew developments on Windows Phone 7!!

Microsoft will soon support homebrew developments on their Windows Phone 7 platform following two days of meetings with developers behind the ChevronWP7 unlocking tool.
Late last year following the release of Windows Phone 7, a team of developers uncovered a bug which allowed those with a device running the operating system to install applications on their device without using Microsoft's application store, dubbed the Marketplace.
It made headlines as technology enthusiasts fought over whether the release of the unlocking tool, ChevronWP7, was a good idea to enable freedom on the platform or if it was a bad idea, encouraging jailbreaking and piracy.
However the team behind the software were soon contacted by Microsoft's Brandon Watson, Director of Developer Experience for Windows Phone 7, who took a keen interest in the matter and encouraged the developers to cease offering the tool while discussions about ChevronWP7's future continued between Microsoft and the developers.
Fast track to today, and the future is looking bright for developers and users alike seeking to install apps or customise their Windows Phone 7 device further than the Marketplace allows. In a blog post on the ChevronWP7 website, developers Rafael Rivera, Chris Walsh and Long Zheng confirm the software giant will soon offer an official way for people to "homebrew" develop on their devices, although just how this will happen is still being discussed.
"We're collaborating with Microsoft on an interim solution that will continue to support homebrew developments after the update," the trio wrote. "We will share details of this when it has been finalized."
The breakthrough comes following a two day meeting held at Microsoft's Redmond campus earlier in the month, which Rivera, Walsh and Zheng were invited to. Microsoft confirmed during the meetings that an update will be pushed out "soon" which will fix the bug which allowed the Chevron WP7 tool to work, rendering the unlocking tool useless.
The future isn't looking too gloomy though, with the trio "genuinely excited" about what the future holds for Windows Phone 7, saying they'll continue to work with Microsoft to "support mutual goals of broadening access to the platform while protecting intellectual property and ensuring platform security."
"We appreciate Microsoft's outreach, genuine interest and involvement in this matter and we hope the community can understand we're working towards a win-win scenario."
http://www.chevronwp7.com/post/2885085987/a-first-step-in-the-right-direction
If MS can pull off allowing side loading whilst preventing paid for apps from being pirated then this could be huge.
Even more huge would be if they finally start to offer the paid apps worldwide and not only in 20 countries. It's really abusing when you buy a 500 Euro phone and you can't get the really good apps and games for it even if you want to pay And that's true even for most EU countries.
It's really funny that MS expect me not to pirate WP7 apps but at the same time they offer me no legal way to buy them
TheOnly1 said:
Even more huge would be if they finally start to offer the paid apps worldwide and not only in 20 countries. It's really abusing when you buy a 500 Euro phone and you can't get the really good apps and games for it even if you want to pay And that's true even for most EU countries.
It's really funny that MS expect me not to pirate WP7 apps but at the same time they offer me no legal way to buy them
Click to expand...
Click to collapse
Sod it, just pirate them and give the money you would have spent to a charity of your choice
Confused !
i dont get it !!!!! what is the good point in it for us that using chevron unlocker and it will be patched soon !?
Chevron will die with the official update, but an even better unlocker is already done and waiting just for the update to be released, so that MS don't accidentaly shut it out
TheOnly1 said:
Chevron will die with the official update, but an even better unlocker is already done and waiting just for the update to be released, so that MS don't accidentaly shut it out
Click to expand...
Click to collapse
Might as well post the link so other xda users know where to go to get it.
Windows Phone Device Manager
http://touchxperience.com/
I wonder when the penny dropped with MS. They've lost a lot of ground to Apple and Android - I'm confident they'll catch up, but they'll have to make more of an effort by giving stuff out for free.
For me, for now, I'm back to Android. WP7 was quick and slick, but like Kelly Brook, nice to look at but not a lot going on below the surface.
TheOnly1 said:
Chevron will die with the official update, but an even better unlocker is already done and waiting just for the update to be released, so that MS don't accidentaly shut it out
Click to expand...
Click to collapse
Yes are right !!!!!!!!!!!!!!!!!!!!!!!!!!1 there is nothing impossible so if chevron die the other hacker and developer will rise ! , it is my personal war between me and MS ! cuz of '3 bottuns " !!!!

[UPDATE] - Windows Phone 7 update on February 7

I hope e this is try, and can run in our beautifful HD2.
...because i can't leave without Copy\Past feature in a smarthone SO....until that, i'm on Android scene.
http://www.winrumors.com/rumor-windows-phone-7-update-on-february-7/
Windows Phone 7 update on February 7
54 minutes ago...
Microsoft may be gearing up to release its first Windows Phone 7 update on February 7 according to reports.
LiveSide has tracked a number of French sites that suggest Microsoft will release its first Windows Phone 7 update on February 7. There’s no proof that the date is accurate and the timing is odd given that Microsoft chief Steve Ballmer will be in Barcelona on February 14 for the Mobile World Congress. Whether or not the date is accurate, WinRumors can confirm that Microsoft has Released to Manufacturing (RTM) its first update codenamed “NoDo”.
Microsoft’s first update will improve application start-up and resume times and introduce the important copy and paste feature. Microsoft posted a support article earlier this week that details the update process for Windows Phone 7 devices. The support article has led many to believe that the update is due imminently.
Microsoft revealed earlier this week that it has now shipped 2 million devices to carriers. Microsoft previously revealed that the company had shipped 1.5 million Windows Phone 7 units between the October launch and December. Research firm IDC and application platform Appcelerator recently surveyed over 2,000 developersto work out their intent for 2011. Developer interest for Windows Phone 7 rose 8 points to 36% ‘very interested’ according to the results. IDC says the interest was “due to a better-than-expected launch.” Survey respondents also said that “Windows Phone’s improved UI was a critical factor for the increase.”
Microsoft also revealed there are now 24,000 registered Windows Phone developers and over 6,500 applications in the marketplace. Microsoft’s customer satisfaction rates on Windows Phone handsets are at 93% according to the company. Microsoft is believed to be planning to unveil a second bigger update in February at the Mobile World Congress show in Barcelona, Spain. Microsoft’s second update will introduce enhanced developer controls for applications and updated Silverlight components.
Joe Belfiore, who oversees Windows Phone Program Management, and is responsible for the design and software product definition of forthcoming generations of Windows phones will keynote MIX11 this year. Belfiore is expected to layout a roadmap for the future of Windows Phone 7 and detail Microsoft’s second Windows Phone 7 update. Microsoft is also working on a major overhaul of the Windows Phone 7 browser. In a job posting, listed in November, the software maker promises a “major overhaul of standard support and new approaches to make significant advances in performance, power consumption and bandwidth utilization.” Microsoft may be ready to detail its future Internet Explorer mobile plans at MIX in April too. Microsoft is believed to be planning Flash and HTML5 support for Windows Phone 7.
Click to expand...
Click to collapse
Lets wait, and see if Microsoft wants ot not, more embassatores for WP7s.....
From what i'm reading it seems to me that microsoft won't block htc hd2 phones, they want developers to go to windows phone 7, they want ratings to go up.
So to me is they won't block access for htc hd2's.
After the update...
Microsoft, does NOT want hackers and independent developers modifying their OS. The HTC HD2 will be excluded from the update. If Microsoft wanted this and other devices like it on the new OS, they would lighten up on their restrictions. After all THEY are the ones that control it.
The WP7 update will close the bug that allows the Chevron tool to work. Our only hope is that someone will hack the update to work. It's going to be much harder this time, as MS had some help and insight from the Chevron guys! Time will tell us for sure.
I actually don't understand how Microsoft could exclude the HD2 from the update, given the current architecture. Their own Marketplace servers think the HD2 is an HD7... if they could detect the difference, they would have blocked us already.
We know that Microsoft has designed the WP7 to have complete and total seperation between the OEM and carrier's device-specific modules on the one hand, and the vanilla OS on the other. Microsoft's updates are exclusively for the latter portion of the OS, which is why they can push out a single update package to all unlocked devices *directly*.
In short, my money is on the first update working just fine for the HD2, breaking very little in the process. It isn't a question of what Microsoft secretly wants. This is about HTC building the HD7 out of almost all the same hardware as the HD2, and any small differences were easily patched up by DFT.
I might add that since Microsoft has triumphantly announced that NoDo will break ChevronWP7, wouldn't you expect them to also announce that they had closed an HD2 loophole?
benjaminries said:
I actually don't understand how Microsoft could exclude the HD2 from the update, given the current architecture. Their own Marketplace servers think the HD2 is an HD7... if they could detect the difference, they would have blocked us already.
We know that Microsoft has designed the WP7 to have complete and total seperation between the OEM and carrier's device-specific modules on the one hand, and the vanilla OS on the other. Microsoft's updates are exclusively for the latter portion of the OS, which is why they can push out a single update package to all unlocked devices *directly*.
In short, my money is on the first update working just fine for the HD2, breaking very little in the process. It isn't a question of what Microsoft secretly wants. This is about HTC building the HD7 out of almost all the same hardware as the HD2, and any small differences were easily patched up by DFT.
I might add that since Microsoft has triumphantly announced that NoDo will break ChevronWP7, wouldn't you expect them to also announce that they had closed an HD2 loophole?
Click to expand...
Click to collapse
I appreciate your train of thought, and love the optimism
Is there something like a kudos button here?
neugroove said:
I appreciate your train of thought, and love the optimism
Is there something like a kudos button here?
Click to expand...
Click to collapse
No, But he just said it
MS will surely shut down that bug on their os and no longer hd2 with wp7 ,but for surely they will hack into it , MS answered me that porting WP7 to HD2 WAS NOT ILEIGAL
benjaminries said:
I actually don't understand how Microsoft could exclude the HD2 from the update, given the current architecture. Their own Marketplace servers think the HD2 is an HD7... if they could detect the difference, they would have blocked us already.
We know that Microsoft has designed the WP7 to have complete and total seperation between the OEM and carrier's device-specific modules on the one hand, and the vanilla OS on the other. Microsoft's updates are exclusively for the latter portion of the OS, which is why they can push out a single update package to all unlocked devices *directly*.
In short, my money is on the first update working just fine for the HD2, breaking very little in the process. It isn't a question of what Microsoft secretly wants. This is about HTC building the HD7 out of almost all the same hardware as the HD2, and any small differences were easily patched up by DFT.
I might add that since Microsoft has triumphantly announced that NoDo will break ChevronWP7, wouldn't you expect them to also announce that they had closed an HD2 loophole?
Click to expand...
Click to collapse
I wish I shared your optimism and hope you are correct, but from what I can understand, the update will effectively push out a new ROM having backed up the old one first.
Whatever black magic the DFT guys did to hack the ROM to work on HD2 would surely be undone? I therefore believe we won't get the update unless and until the DFT hack it.
There could be stuff below the ROM level that won't be affected and it could be this stuff that DFT tweaked - not knowing the architecture of WP7 I couldn't comment.
Being a pessimist, it just feels too good to be true that a update would work without any issue - hope I'm wrong though. This could be how MS propose to close the HD2 loophole. It would even work quite well for MS. Having had a taste of WP7, how many of us might go out and buy a WP7 phone having had an extended trial and then being cut off from our dealer...
Gustopher said:
I wish I shared your optimism and hope you are correct, but from what I can understand, the update will effectively push out a new ROM having backed up the old one first.
Whatever black magic the DFT guys did to hack the ROM to work on HD2 would surely be undone? I therefore believe we won't get the update unless and until the DFT hack it.
There could be stuff below the ROM level that won't be affected and it could be this stuff that DFT tweaked - not knowing the architecture of WP7 I couldn't comment.
Being a pessimist, it just feels too good to be true that a update would work without any issue - hope I'm wrong though. This could be how MS propose to close the HD2 loophole. It would even work quite well for MS. Having had a taste of WP7, how many of us might go out and buy a WP7 phone having had an extended trial and then being cut off from our dealer...
Click to expand...
Click to collapse
Yeah right, I wouldn't buy the same hardware again, I would consider if at least any of the wp7 phones get the Desire HD hardware, but none of them has it. If the update stop us from wp7 then I'll stick with android and wait for the next major hardware upgrade then I will look for another phone.
Voluntary update?
My understanding is that the update will not mandatory.
You can choose to update you system or not. So our HD27's will still work once the update is released - we just wont have the new features or be able to run apps that use the new featrues.
I thinks the chances of the update working are fair to good. From what I have gathered the biggest problem the DFT team had was getting magldr and the WP7 OS to play well together from NAND.
I may be wrong - but I like the "glass half full approach".....
I don't think you could update the hd2 , and if I was DFT I had prevented it from updating to (just to be sure that there are after a update no 14000 bricks)
i wouldn't be surprised if the HD2 could flawelessly get the update. Since it is an MS update, none of the hardware specific software/drivers will be affected. Otherwise, MS has to push updates for specific devices and that is not what they are planning to do. But who'll know? I am sure to be the first to try that out and if I will brick my device, than so be it. I don't think the HD2 can be bricked beyond repairing. With all the great tutorials, first aid guides here on XDA, I think it is safe to try it.
benjaminries said:
I actually don't understand how Microsoft could exclude the HD2 from the update, given the current architecture. Their own Marketplace servers think the HD2 is an HD7... if they could detect the difference, they would have blocked us already.
We know that Microsoft has designed the WP7 to have complete and total seperation between the OEM and carrier's device-specific modules on the one hand, and the vanilla OS on the other. Microsoft's updates are exclusively for the latter portion of the OS, which is why they can push out a single update package to all unlocked devices *directly*.
In short, my money is on the first update working just fine for the HD2, breaking very little in the process. It isn't a question of what Microsoft secretly wants. This is about HTC building the HD7 out of almost all the same hardware as the HD2, and any small differences were easily patched up by DFT.
I might add that since Microsoft has triumphantly announced that NoDo will break ChevronWP7, wouldn't you expect them to also announce that they had closed an HD2 loophole?
Click to expand...
Click to collapse
They can detect it from IMEI, first 8 digits state the manufacturer and model. There are DBs on the net to verify IMEI against phone maker and model. e.g. imei-number.com/tac-list
MerLinh said:
Yeah right, I wouldn't buy the same hardware again, I would consider if at least any of the wp7 phones get the Desire HD hardware, but none of them has it. If the update stop us from wp7 then I'll stick with android and wait for the next major hardware upgrade then I will look for another phone.
Click to expand...
Click to collapse
Fair point. Until DFT WP7 I was at a loss though; WM6.5.5 is dying through lack of new stuff, I didn't fancy WP7 and having had a play with Android it just irritates me - I know it can be changed but the default colour scheme and design looks like it was done by a class of 7 year olds with a box of crayons (NB: my opinion, apologies Android-lovers).
So at least I know now that I could go out and buy a WP7 device, but you are quite correct that the launch phones are a disappointing bunch, with nothing one whit better than my HD2.
I have a hunch that something sexy must be coming as WP7 slowly gathers momentum, so I'll hang onto my money for now.
What to do if the update breaks the HD2(7) though...
(Accepting that it may well be optional and might well not break it even then)
hyellow said:
i wouldn't be surprised if the HD2 could flawelessly get the update. Since it is an MS update, none of the hardware specific software/drivers will be affected. Otherwise, MS has to push updates for specific devices and that is not what they are planning to do. But who'll know? I am sure to be the first to try that out and if I will brick my device, than so be it. I don't think the HD2 can be bricked beyond repairing. With all the great tutorials, first aid guides here on XDA, I think it is safe to try it.
Click to expand...
Click to collapse
Huh, I wouldn´t count on that. I can definitely imagine the updater could be able to detect the phone you are using (many of us showing "HD7") and upload specific drivers, too - the original WP7 devices did receive some updates already. To make the updates user friendly, they maybe include those brand/operator specific files and drivers, who knows. And replacing the DFT/Leo70 driver material with original HD7 versions might maybe brick the system...
galatei said:
They can detect it from IMEI, first 8 digits state the manufacturer and model. There are DBs on the net to verify IMEI against phone maker and model. e.g. imei-number.com/tac-list
Click to expand...
Click to collapse
Now that seems to be a bit far stretched... but who knows... modern times, no?
At least, it would kind of confirm my thoughts above...
It could be that we may get the update and install it OTA,but in absence of any immediate DFT or Chevron Development efforts we could very well get stuck with WP7 on our HD2s !!!.
I'm pretty sure we won't be able to update our phones successfully with MS's update... we'll probably have to wait until DFT releases an update to flash manually. But unless DFT pre-hacks the registry to make it show up as a HD7, we will have problems doing anything with it until a new way to unlock it is discovered. We'll have to wait and see what happens, but we will probably be stuck without updates for a while I think.
the only update i am looking forward to is massively improved battery life, this has to be from DFT.
haksam said:
the only update i am looking forward to is massively improved battery life, this has to be from DFT.
Click to expand...
Click to collapse
Really? How can you live without Copy \ Past feature? I use WP7s for 3 days, and was very annoying without that feature.
And I miss, only copy /past but too, more share options and multitasking.... I like very much the UI, but I need quickly this features added.
Sent by my HD2 Gingerbread device
benjaminries said:
I actually don't understand how Microsoft could exclude the HD2 from the update, given the current architecture. Their own Marketplace servers think the HD2 is an HD7... if they could detect the difference, they would have blocked us already.
We know that Microsoft has designed the WP7 to have complete and total seperation between the OEM and carrier's device-specific modules on the one hand, and the vanilla OS on the other. Microsoft's updates are exclusively for the latter portion of the OS, which is why they can push out a single update package to all unlocked devices *directly*.
In short, my money is on the first update working just fine for the HD2, breaking very little in the process. It isn't a question of what Microsoft secretly wants. This is about HTC building the HD7 out of almost all the same hardware as the HD2, and any small differences were easily patched up by DFT.
I might add that since Microsoft has triumphantly announced that NoDo will break ChevronWP7, wouldn't you expect them to also announce that they had closed an HD2 loophole?
Click to expand...
Click to collapse
actually, think about it, there is one single blindingly obvious difference thats so easy to detect they could get a 10 year old to locate them.
How many buttons do you have on your HD2? i wouldnt be sure there was no way of knowing. even if we take that out you'll still have some kind of unique signature on the cracked OS that we have all used, it would be near on impossible to hide the fact its an HD2 and not an HD7 if they really wanted to find out.

The HTC seems not to unlock the hboot .v.

here!!
(In Traditional Chinese)
Only HTC doesn't seem to unlock the hboot now!!
For those wondering here is a google translate version of the text on the page - that is why it is in bad english
Sony Ericsson last month promotional offer for mobile phone unlocking Bootloader, as it were the entire mobile phone industry has some new territory like. Samsung announced soon also Twitter 『If Google does not oppose, they will also unlock the phone Bootloader』. Motorola has been silent today audible.
Motorola promised by the end of this year's Android device for its offer unlocking services, users can own brush from a ROM.
Now even unlock a Motorola also provides that only four brands in the Android HTC did not respond due to the unknown when it said it will adhere or surrender it.
Click to expand...
Click to collapse
Sounds like HTC made no commnet
So I would say this article is one way or another. Plus maybe something is lost in that translation a little.
HTC, to this point, seems pretty good with being unlocked. I've had my Evolution now since it came out and its fully customized. The new Evolution after it also looks that way. I really thing, aside from Motorola, that the carriers may start being he ones to ask to lock or unlock he bootloaders. ISPs in the US finally out caps on bandwidth last year, I would see locked bootloaders being next. Really time will only tell, but hopefully we get to keep our freedoms. The FCC approved a device is ours when we buy it, therefore we should be able to do what we want. Hopefully companies keep that in mind instead of trying to lock stuff down.
The big business rreason is that an unlocked device lets a user stay with that device longer, as it can be customized wig the latest software features. Unlocked devices really force companies to invest in research to give us better hardware now, costing them more money. As anyway can really developed the software that goes into the phones.
My thoughts anyway...
~Max
√ This Message Sent From CM7 Nightlies HTC-Evo4G ™

Blackberry's Patching blog post

From the official Blackberry blog: http://blogs.blackberry.com/2015/11/managing-android-security-patching-for-priv/
One quote that stands out to me is this: "While BlackBerry will work with its go-to-market partners on approval and delivery of hotfixes, BlackBerry has the ability to directly patch all PRIV variants and will do so when necessary to protect users and enterprises."
Does this mean Blackberry is now alone with Apple with the ability to directly push an update to carrier bought phones? I know Nexus devices get updates right away, but I think I'm correct in saying you can't get one through a carrier.
Going through a carrier? I'll believe it when I see it!
My biggest concern is that they'll push updates for a year, maybe a year and a half and then stop. It's great that the device is locked down but without an alternative method of securing the device, e.g. another rom with updated Android patches, that'd be a sorry state of affairs.

Categories

Resources