lotreaglesfan

Phone has been on sbl.bin while running ODIN3EXECUTION 1.00 for the past 5 minutes. Hoping I haven't screwed myself. I have to send the phone back to Samsung so I wanted to make sure that it was running complete stock since I rooted and deleted the Mobile AP app and such.

How long does ODIN take on this? :\

__________________
Isaiah 41:10

lotreaglesfan

<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> Sbl.bin

lotreaglesfan

now its stuck on <ID:0/007> boot.bin

so i guess it's very slowly doing it?

pac0naut

Hrm....didn't take me that long to flash. Did you do a complete wipe first?

Dante04SRT

A normal stock flash with Odin takes ~3 minutes.

The SBL and Boot files have to do with the Bootloader. This is a really nasty area to get stuck at - If your phone doesn't reboot anymore (goes black, doesn't power on), then you are hard bricked - There is no simple fix for this.

I always sigh with relief every time ODIN gets past that during the flash to stock process.

__________________
Samsung Captivate
Running Froyo 2.2 - Serendipity 6.2
Previously: Andromeda 1.2. Continuum 3.1.1, FireFly 2.3, Cognition v3.04/4.1, Paragon RC6

lotreaglesfan

i'm hard bricked :'(

thiswasatriumph

Well it doesn't hurt to try the usb unbricking jig trick. one example- [FIX] Unbrick captivate w/o cutting up USB! - xda-developers

Dante04SRT

You could try that, but once the SBL.bin file is damaged/lost, the jig isn't gonna fix anything.