Commentary

Live Report Part 3: I Have The 3G iBrick, Er, iPhone

After four and a half hours, I walked away from the Apple store only partly victorious. I was able to buy a 3G iPhone, but it couldn't connect to the iTunes server to activate, and is thus a brick at the moment.

After four and a half hours, I walked away from the Apple store only partly victorious. I was able to buy a 3G iPhone, but it couldn't connect to the iTunes server to activate, and is thus a brick at the moment.Two problems with the entire purchasing experience: AT&T's servers, and the iTunes servers.

First, the AT&T servers were overwhelmed, preventing access to existing accounts and blocking people from creating new accounts or whatever changes were necessary to set up an account with the 3G iPhone. If this first step was successful, then you moved to step No. 2: Authentication via the iTunes server.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The first step took time, and often had to be repeated before things would go through. Eventually, however, it worked for me.

Step two was (and still is) a problem. The iTunes server continues to struggle with the onslaught of requests and can't be reached. In the end, after several unsuccessful activation attempts, Apple allowed me to walk away with an unactivated phone. The representatives at the Apple Store told me to continue to try to authenticate it through the iTunes server once I got home.

I've been trying for 30 minutes now with no luck. So I have an iBrick that can only make emergency calls. My old iPhone already has been deactivated, and can no longer make or receive calls.

Hopefully the iTunes server will respond and let me activate the phone at some point...


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