forum home page
register faq member list calendar search
MacShock.com - Apple Forums
Reload this Page
Old 11-12-2011, 04:50 PM
Bert
Guest
 
Posts: n/a
Default Avoid bricking an "original" iPad?

I've seen (just) a few reports of folks whose original iPads turned into
paperweights after attempting to move from iOS 4.x to 5.x.

Has anybody been able to figure out what went wrong for those folks? Was
it just bad luck, or are there some easily avoidable pitfalls?

Now that Stanza's been fixed for 5.0.1 but no longer works on 4.x, I'm
inclined to move up.

--
bert@iphouse.com St. Paul, MN
  Reply With Quote
Old 11-12-2011, 04:50 PM
Gerry
Guest
 
Posts: n/a
Default Avoid bricking an "original" iPad?

In article <Xns9F9B6DD9A6C3VeebleFetzer@216.250.188.141>,
Bert <bert@iphouse.com> wrote:

> I've seen (just) a few reports of folks whose original iPads turned into
> paperweights after attempting to move from iOS 4.x to 5.x.
>
> Has anybody been able to figure out what went wrong for those folks? Was
> it just bad luck, or are there some easily avoidable pitfalls?
>
> Now that Stanza's been fixed for 5.0.1 but no longer works on 4.x, I'm
> inclined to move up.


I did a quick search on "Original iPad and iOS 5" and the only problems
that I could find is the lack of the multi-touch gestures, which has
been corrected in iOS 5.01.

A report from MacWorld had Amazon hinting that this may be the last
upgrade to Stanza no further upgrades are planned.
  Reply With Quote
Old 11-12-2011, 06:20 PM
Bert
Guest
 
Posts: n/a
Default Avoid bricking an "original" iPad?

In newsnce-C4E2E3.09491912112011@news.eternal-september.org Gerry
<once@around-the-block.org> wrote:

> A report from MacWorld had Amazon hinting that this may be the last
> upgrade to Stanza no further upgrades are planned.


They also said that they wouldn't be providing a version to work on iOS
5.

Now that they've alienated (at least temporarily) all those folks who
either choose to or have to stay on iOS 4.x, maybe they'll thing again,
again.

--
bert@iphouse.com St. Paul, MN
  Reply With Quote
Old 11-12-2011, 06:20 PM
Carl Heinz
Guest
 
Posts: n/a
Default Avoid bricking an "original" iPad?

On 12 Nov 2011 17:55:14 GMT, Bert <bert@iphouse.com> wrote:

>Now that they've alienated (at least temporarily) all those folks who
>either choose to or have to stay on iOS 4.x, maybe they'll thing again,
>again.


I reinstalled Stanza after going to 5.0.1 and it appears to be working ok.
--
Carl Heinz
cfheinz57@charter.net
(Remove number)
  Reply With Quote
Old 11-12-2011, 06:20 PM
Bert
Guest
 
Posts: n/a
Default Avoid bricking an "original" iPad?

In news:cddtb7dgfpi9iqlaqde12dq1nuirnggk5s@4ax.com Carl Heinz
<cfheinz57@charter.net> wrote:

> On 12 Nov 2011 17:55:14 GMT, Bert <bert@iphouse.com> wrote:
>
>>Now that they've alienated (at least temporarily) all those folks who
>>either choose to or have to stay on iOS 4.x, maybe they'll thing
>>again, again.

>
> I reinstalled Stanza after going to 5.0.1 and it appears to be working
> ok.


That's right; the current version of Stanza no longer works on 4.x, only
on 5.x.

--
bert@iphouse.com St. Paul, MN
  Reply With Quote
Old 11-13-2011, 02:50 PM
Wayne Marsh
Guest
 
Posts: n/a
Default Avoid bricking an "original" iPad?

In article <Xns9F9B6DD9A6C3VeebleFetzer@216.250.188.141>,
Bert <bert@iphouse.com> wrote:

> I've seen (just) a few reports of folks whose original iPads turned into
> paperweights after attempting to move from iOS 4.x to 5.x.
>
> Has anybody been able to figure out what went wrong for those folks? Was
> it just bad luck, or are there some easily avoidable pitfalls?


It happened to me. I don't know to avoid it, but I did find how to fix
it, as I posted here a few days ago:

"Recapping: My original iPad failed on an attempted upgrade to IOS 5
with infamous "unknown error (1)". All of my attempts to recover failed.
Apple Store "genius" pronounced it dead.

Turns out there is a software fix for the apparent iTunes flaw, but it's
offered by the same folks who provide jailbreak software, so Apple has
been actively suppressing the info on the official support forums.

I tried it, and it works. My iPad is now back among the living and
happily running IOS 5. Here's the info:

http://www.cultofmac.com/125326/pote...cked-first-gen
-ipads/

"

--
Wayne Marsh Minneapolis, Minnesota, USA
waynegmarsh@mac.com
  Reply With Quote
Old 11-13-2011, 04:20 PM
Bert
Guest
 
Posts: n/a
Default Avoid bricking an "original" iPad?

In news:Xns9F9B6DD9A6C3VeebleFetzer@216.250.188.141 Bert
<bert@iphouse.com> wrote:

> Now that Stanza's been fixed for 5.0.1 but no longer works on 4.x, I'm
> inclined to move up.


Well, I moved "up" to 5.0.1 and, while I did finally get things working
again, it wasn't a pleasant experience.

One thing I did see while performing the move is the iTunes for Windows
is a really, really bad piece of software. Apple's developers might be
wizards with their own hardware and OS, but they don't do Windows very
well.

During the update process, iTunes spent a lot of time apparently doing
nothing, with no visible sign of activity. I can see how an impatient
or unobservant user might conclude that it was done and terminate it
prematurely, leaving their iThing in an unknown state.

--
bert@iphouse.com St. Paul, MN
  Reply With Quote
Old 11-13-2011, 04:20 PM
Jolly Roger
Guest
 
Posts: n/a
Default Avoid bricking an "original" iPad?

In article <Xns9F9C64DED9E8DVeebleFetzer@216.250.188.141>,
Bert <bert@iphouse.com> wrote:

> In news:Xns9F9B6DD9A6C3VeebleFetzer@216.250.188.141 Bert
> <bert@iphouse.com> wrote:
>
> > Now that Stanza's been fixed for 5.0.1 but no longer works on 4.x, I'm
> > inclined to move up.

>
> Well, I moved "up" to 5.0.1 and, while I did finally get things working
> again, it wasn't a pleasant experience.
>
> One thing I did see while performing the move is the iTunes for Windows
> is a really, really bad piece of software. Apple's developers might be
> wizards with their own hardware and OS, but they don't do Windows very
> well.
>
> During the update process, iTunes spent a lot of time apparently doing
> nothing, with no visible sign of activity. I can see how an impatient
> or unobservant user might conclude that it was done and terminate it
> prematurely, leaving their iThing in an unknown state.


It was probably restoring apps and data back to the iPad, which can take
quite a while over USB and even longer over WiFi.

--
Send responses to the relevant news group rather than email to me.
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.

JR
  Reply With Quote
Old 11-13-2011, 05:50 PM
Bert
Guest
 
Posts: n/a
Default Avoid bricking an "original" iPad?

In news:jollyroger-7D4112.10183913112011@news.individual.net Jolly Roger
<jollyroger@pobox.com> wrote:

> In article <Xns9F9C64DED9E8DVeebleFetzer@216.250.188.141>,
> Bert <bert@iphouse.com> wrote:
>>
>> During the update process, iTunes spent a lot of time apparently
>> doing nothing, with no visible sign of activity. I can see how an
>> impatient or unobservant user might conclude that it was done and
>> terminate it prematurely, leaving their iThing in an unknown state.

>
> It was probably restoring apps and data back to the iPad, which can
> take quite a while over USB and even longer over WiFi.


I have no doubt that it was very busy doing something very important;
unfortunately, it gave no external indication, not even so much as an
hourglass.

--
bert@iphouse.com St. Paul, MN
  Reply With Quote
Old 11-14-2011, 08:30 AM
Leonard Blaisdell
Guest
 
Posts: n/a
Default Avoid bricking an "original" iPad?

In article <Xns9F9C79632E79EVeebleFetzer@216.250.188.140>,
Bert <bert@iphouse.com> wrote:

> In news:jollyroger-7D4112.10183913112011@news.individual.net Jolly Roger
> <jollyroger@pobox.com> wrote:


> > It was probably restoring apps and data back to the iPad, which can
> > take quite a while over USB and even longer over WiFi.

>
> I have no doubt that it was very busy doing something very important;
> unfortunately, it gave no external indication, not even so much as an
> hourglass.


I helped a family member upgrade from iOS4 to iOS5.01 today on a Win
machine. I was mostly moral support since I know zip about Windows but
had upgraded a iPhone4 on a Mac. The time to disconnect was not obvious.
There were times when she wanted to, but I had her start her iPhone
while it was still connected to the USB port. Something on one of the
machines always indicated to not disconnect.
When the iOS was finally loaded to her computer, there was no prompt to
stay connected or disconnect. Fortunately, there was a progress bar that
went to work on her iPhone. When the progress bar filled and she was
ready to disconnect, a brief message came up on her computer that the
iOS was loaded at factory settings.
Had she disconnected then, she would probably have had just that. But we
hung in there. Then came current iPhone settings, then came Apps, then
came Ringtones, then came etc. Then came firmware settings, and maybe we
were done, but I don't remember.
At any rate, after the firmware update, I wakened the iPhone still
plugged in and had iCloud settings to fiddle with. We were home free.
On her Windows 7 system with iTunes, things didn't appear as obvious to
me as on my Mac. We easily could have disconnected way too early. This
may be a problem for some upgrading to iOS5 on Windows 7. Patience!

leo
  Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 03:14 PM.
Copyright ©2007-2008 MacShock.com. Powered by vBulletin
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.