<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>3.0.1 on Tony Andrew Meyer</title><link>http://tonyandrewmeyer.com/tags/3.0.1/</link><description>Recent content in 3.0.1 on Tony Andrew Meyer</description><generator>Hugo</generator><language>en-nz</language><lastBuildDate>Mon, 03 Aug 2009 11:24:26 +1200</lastBuildDate><atom:link href="http://tonyandrewmeyer.com/tags/3.0.1/index.xml" rel="self" type="application/rss+xml"/><item><title>My 2GB, 4 day 0.0.1 iPhone update</title><link>http://tonyandrewmeyer.com/2009/08/03/my-2gb-4-day-0-0-1-iphone-update/</link><pubDate>Mon, 03 Aug 2009 11:24:26 +1200</pubDate><guid>http://tonyandrewmeyer.com/2009/08/03/my-2gb-4-day-0-0-1-iphone-update/</guid><description>&lt;p>A few days ago, &lt;a href="http://apple.com">Apple&lt;/a> released version &lt;a href="http://support.apple.com/kb/HT3754">3.0.1&lt;/a> of the iPhone OS, which addressed a pretty major SMS vulnerability.  When Olyvia tried updating her 3GS to 3.0.1, something went wrong.  The iPhone entered &amp;ldquo;Recovery Mode&amp;rdquo;, which means that it displays an image indicating that you need to connect it to iTunes, and you can&amp;rsquo;t do anything else (no phone calls, no iPod, no applications - absolutely nothing).  Connecting the phone to iTunes prompted a message indicating that the phone needed to be recovered - doing so downloaded the 3.0.1 update, and then got stuck on the &amp;ldquo;Verifying Restore with Apple&amp;rdquo; step for a long time, until it would finally fail with error &amp;ldquo;3104&amp;rdquo;.  This process could then be repeated, with the same results.
What this meant in practice was that the phone was bricked as of last Friday.  &lt;strong>An update should never be able to brick a (legitimate, not jailbroken) phone!&lt;/strong> Even more, failing to verify a restore with Apple should never leave the phone in a broken state.
I tried many thing to resolve this:&lt;/p></description></item></channel></rss>