• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Captivate bricked during 2.2 update

E

Euphoria14

Lurker
Hi, I just tried updating my 2.1 Captivate to 2.2 using Samsung Kies and the install wouldn't go beyond 0%.

After waiting a while (~30 mins) it was still sitting at 0%.

Anyways now my phone is completely bricked. Emergency recovery wouldn't go beyond 0% and after looking up solutions I found a program called Odin3 one-click.

Odin3 One-Click, after putting my phone into download mode, hangs every single time at sbl.bin.


I still have 1 1/2 years left on my plan with AT&T. Am I screwed here? If so I am very upset. Why couldn't they have just done this update over the air?
 
Euphoria14 said:
Hi, I just tried updating my 2.1 Captivate to 2.2 using Samsung Kies and the install wouldn't go beyond 0%.

After waiting a while (~30 mins) it was still sitting at 0%.

Anyways now my phone is completely bricked. Emergency recovery wouldn't go beyond 0% and after looking up solutions I found a program called Odin3 one-click.

Odin3 One-Click, after putting my phone into download mode, hangs every single time at sbl.bin.


I still have 1 1/2 years left on my plan with AT&T. Am I screwed here? If so I am very upset. Why couldn't they have just done this update over the air?
Click to expand...

If you can still get the phone INTO Download Mode, you're probably all right. You have two options:

(a) Take the phone into ATT and explain that the Kies update failed and your phone is broken.

or

(b) Use ODIN again (NOT the one-click one), and try again - I've never seen a phone that COULD get to Download Mode that wasn't fixable.
 
Dante04SRT said:
If you can still get the phone INTO Download Mode, you're probably all right. You have two options:

(a) Take the phone into ATT and explain that the Kies update failed and your phone is broken.

or

(b) Use ODIN again (NOT the one-click one), and try again - I've never seen a phone that COULD get to Download Mode that wasn't fixable.
Click to expand...

Thank you for the reply, but anywhere I could go that would explain exactly how I could do that without the one-click?

Also, could AT&T perform the update on my phone in it's current state at the store?
 
I've noticed an apparent bug of Odin is that you must plug the device in AFTER running Odin. A strange quirk that can cause confusion, needless to say. Not that it has anything to do here, lol.
 
Euphoria14 said:
Thank you for the reply, but anywhere I could go that would explain exactly how I could do that without the one-click?

Also, could AT&T perform the update on my phone in it's current state at the store?
Click to expand...

Glad to hear you got it fixed - As for ATT fixing it; It's unlikely - I doubt their average store knows much of anything.
 
Glad you got it fixed, sorry I posted an irrelevant comment ;p. To post more irrelevant comments about my own reversion...

I was working on going back to stock myself, which I've now done with the help of Kies Mini -- no thanks to it crashing on my Win7 x64 box, but not on my Win7 x64 laptop. The OTA update kept failing at 50%, but Kies worked fine.

Why did I go back to stock? Well, honestly, I don't completely trust non-stock firmwares, or firmwares that I don't know the author of personally. Sure, maybe a little paranoid, but everything is on the phone -- including Google Authenticator (Google's new double authentication method). I simply must have a secure OS, and short of examining all components of the firmware, I can't do that. So, I'll stay with stock on this device. Also, there is always the possibility that unknown changes, while seeming benign to the developer, may have unintended consequences.

That said, all the custom ROMs out there are great. The final call for me was actually when Swype went braindead, losing its dictionary somehow. I have no idea how this suddenly occurred, but the only fix seemed to be a full factory restore/reset. I'm sure another fix was likely possible, but I was unable to easily do it with simple actions such as clearing its cache, or restoring its user data from a previous backup.

And going to ATT stores is a crap shoot, just like anything.. You can encounter an idiot or a guru.
 
UPDATE: I found out that the Swype issue was universal across all third-party firmwares. The copy they were using expired ;o. Apparently the only 'solution' is to switch to the beta swype, after doing a manual uninstall of Swype and deleting its library from the phone (else the beta swype will refuse to install).

Lastly, to any and all readers, watch what permissions applications request. Applications should request what they need and *no more*. Be wary of applications that request excessive rights, unless known to be trusted.
 
I have nearly the same problem as OP - Samsung Captivate, wanted to update from 2.1 to 2.2 by following this:
How Do I Update The Software On My AT&T SGH-i897 (Captivate) Phone To Android 2.2 (Froyo) Through Kies Mini For PC?
which didn't work. The only things I can get my phone to do are to display the phone-exclamation mark-computer and the yellow triangle which says 'Downloading' underneath.

I've tried Odin One-click, and it always stalls on File Analysis - how long is it supposed to take?
 
I finally got it to work -- I tried using Odin on Windows XP, and it worked pretty flawlessly. All of my apps and wallpapers were deleted, but that's expected, I guess. I can just download them again.
 
I bricked mine during the update too. Took it to an AT&T store, they had no clue how to fix it, but at least they got on the phone with support, did the basic steps (it was truely bricked) and got the OK to replace my phone. Had to drive to the AT&T refubish center (or whatever it's called), they gave me a new phone there, swapped out my sd card. (I was also 6 months into the new phone) The girl there told me some of the older Captivates aren't able to be updated to 2.2, but I'm not sure she knew what she was talking about.

I had backed up everything to my sd card anyway, and my contacts were all on google. I restored to the new phone, and tried the update again later that day, it worked like a charm.
 
You must log in or register to reply here.
Back
Top Bottom