warning: Gingerbread can brick Captivate

Yesterday I got an ATT text message saying the Gingerbread update was
available for my Samsung Captivate. During the firmware update, it gave
an error message saying it had a problem and I should remove, then
replace, the battery, then try again. After the battery maneuver the
phone was dead. Emergency reboot did not work. It's now with UPS going
to Samsung. Its SIM card is in its predecessor dumb(but working)phone.
On forums.att.com I see I'm not the only one this has happened to.

In article <jgkg8l$dr9$1@speranza.aioe.org>, tmoran@acm.org wrote:

> Yesterday I got an ATT text message saying the Gingerbread update was
> available for my Samsung Captivate. During the firmware update, it gave
> an error message saying it had a problem and I should remove, then
> replace, the battery, then try again. After the battery maneuver the
> phone was dead. Emergency reboot did not work. It's now with UPS going
> to Samsung. Its SIM card is in its predecessor dumb(but working)phone.
> On forums.att.com I see I'm not the only one this has happened to.

take it back, get an iPhone, problem solved.

On 3/13/2012 8:24 AM, Elmo P. Shagnasty wrote:
> In article
> <apony-598B1D.22552012032012@dialup-4.167.115.65.dial1.houston1.level3.n
> et>,
> Oxford<apony@pasture.com> wrote:
>
>> In article<jgkg8l$dr9$1@speranza.aioe.org>, tmoran@acm.org wrote:
>>
>>> Yesterday I got an ATT text message saying the Gingerbread update was
>>> available for my Samsung Captivate. During the firmware update, it gave
>>> an error message saying it had a problem and I should remove, then
>>> replace, the battery, then try again. After the battery maneuver the
>>> phone was dead. Emergency reboot did not work. It's now with UPS going
>>> to Samsung. Its SIM card is in its predecessor dumb(but working)phone.
>>> On forums.att.com I see I'm not the only one this has happened to.
>>
>> take it back, get an iPhone, problem solved.
>
> How?

Consider the source: the famous "OxTard"

At 13 Mar 2012 07:48:27 -0400 News wrote:
> On 3/13/2012 8:24 AM, Elmo P. Shagnasty wrote:
> > In article
> > <apony-598B1D.22552012032012@dialup-
4.167.115.65.dial1.houston1.level3.n
> > et>,
> > Oxford<apony@pasture.com> wrote:
> >
> >> In article<jgkg8l$dr9$1@speranza.aioe.org>, tmoran@acm.org wrote:
> >>
> >>> Yesterday I got an ATT text message saying the Gingerbread update
was
> >>> available for my Samsung Captivate. During the firmware update, it
gave
> >>> an error message saying it had a problem and I should remove, then
> >>> replace, the battery, then try again. After the battery maneuver
the
> >>> phone was dead. Emergency reboot did not work. It's now with UPS
going
> >>> to Samsung. Its SIM card is in its predecessor dumb(but working)
phone.
> >>> On forums.att.com I see I'm not the only one this has happened to.
> >>
> >> take it back, get an iPhone, problem solved.
> >
> > How?
>
> Consider the source: the famous "OxTard"


Yep. Someone's mom restored someone's internet access apparently...

> > Yesterday I got an ATT text message saying the Gingerbread update was
> > available for my Samsung Captivate. During the firmware update, it gave
> > an error message saying it had a problem and I should remove, then
> > replace, the battery, then try again. After the battery maneuver the
> > phone was dead. Emergency reboot did not work. It's now with UPS going
> > to Samsung. Its SIM card is in its predecessor dumb(but working)phone.
> > On forums.att.com I see I'm not the only one this has happened to.
To follow up on this message, when I returned from (smartphone-less)
vacation, the repaired phone was waiting for me. They "replaced the
motherboard". The returned phone had Gingerbread installed and works
fine. After reloading from saved stuff, and reinstalling apps, the only
annoyance was that all Contacts were duplicated.