Commentary

Is Anyone Really Surprised That Apple Won't Support Hacked iPhones?

I'm not. And I don't blame them, either. When you buy an iPhone, you implicitly agree to a legal contract in order to use it. Why should they support you if you decide to break the contract?

I'm not. And I don't blame them, either. When you buy an iPhone, you implicitly agree to a legal contract in order to use it. Why should they support you if you decide to break the contract?Contracts exist for a reason: To protect the parties involved and spell out the legal ramifications if terms aren't met. In case you forgot, that terms of use screen that you clicked "Agree" on so you could use your iPhone means you are legally bound to adhere to them (however impractical, arcane, stupid and unintelligible they may be).

I remember when I bought a Gateway computer about 10 years ago, there was a seal along the back panel. It read quite clearly that if the seal was broken (by opening the computer to access its innards), my warranty would be voided. I would wager that somewhere buried in that dense legalese of Apple's terms of use, there are phrases that spell out what happens if you hack or otherwise alter the software of the iPhone by "breaking the seal."


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

If you blithely ignore and break the rules (please understand, though, that I am not saying I really agree with Apple's rules), you've demonstrated that you don't respect Apple's terms of use. When one party breaks a contract, the other is not always beholden to live up to its end of the bargain (in Apple's case, to honor the warranty).

So, iPhone hackers, don't go crying to Apple if your iPhone is bricked by any future firmware updates. You've been warned in no uncertain terms.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links