Commentary

Have An iBrick? Blame The Hackers

A sect of hackers has split from the iPhone Dev Team and claims that AnySIM and iUnlock both had critical flaws that led to the bricking of hacked iPhones during the update to 1.1.1. They place the blame on poorly written hacks by the iPhone Dev Team and have splintered off into their own "elite" team. Fight! Fight! Fight!

A sect of hackers has split from the iPhone Dev Team and claims that AnySIM and iUnlock both had critical flaws that led to the bricking of hacked iPhones during the update to 1.1.1. They place the blame on poorly written hacks by the iPhone Dev Team and have splintered off into their own "elite" team. Fight! Fight! Fight!I think the discussion over who is to blame for bricked iPhones (user, Apple, AT&T) has run its course on this blog, but The Unofficial Apple Weblog (TUAW) and Wired are reporting some new and interesting developments.

Apparently a core of hackers has split from the iPhone Dev Team (IDT) amidst some personal and technical conflicts. One of the hackers, Zibri, was banned from the IDT's IRC channel, and this is what led to the split. The splinter faction has distanced themselves from the IDT and say that AnySIM and iUnlock were flawed because of some Google wiki code buried in the hacks.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The new iPhone Elite Team was harsh in its criticism of the IDT. It said:

No, it wasn't Apple's fault. Rather than figure out how to fix this themselves, the iPhone Dev Team would rather work on jailbreaking the new 1.1.1 and keep accepting your donations. We want this fixed -- we want them to take responsibility for their bunk code.

While it is certainly possible that the hacks were not perfect, I agree with TUAW's stance that since so many unhacked iPhones were also bricked, that the 1.1.1 update wasn't exactly perfect, either.

In the meantime, 1.1.1 has been hacked and a "jailbreak" system is likely to be available to iPhone modifiers imminently.


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