Can I recover my phone?

PumaMania

Active member
Aug 6, 2011
29
4
0
I've been running EH17 stock on my Android for months now. I tried to root back to EC05 using ODIN so I could receive the new update, but now I have no OS. When I try to turn on my phone, a weird little computer connected to a phone pops up instead of the Samsung screen. Download mode still works. But I have tried every possible ODIN combo with no luck.

I can still somehow get access to the original blue Android Recovery. Would a factory reset help, or make things worse? If so, is there any way I can fix this besides ODIN? (I tried One Click Unbrick that simply won't work on my old XP computer)

Please, I'm very desperate here :/
 
I've been running EH17 stock on my Android for months now. I tried to root back to EC05 using ODIN so I could receive the new update, but now I have no OS. When I try to turn on my phone, a weird little computer connected to a phone pops up instead of the Samsung screen. Download mode still works. But I have tried every possible ODIN combo with no luck.

I can still somehow get access to the original blue Android Recovery. Would a factory reset help, or make things worse? If so, is there any way I can fix this besides ODIN? (I tried One Click Unbrick that simply won't work on my old XP computer)

Please, I'm very desperate here :/

Did you try doing Froyo EB13 with Odin? Procedure #2 from the thread below... Seems to work everytime...
[How to] Factory Restore (or Fix a Bricked Phone)
 
Did you try doing Froyo EB13 with Odin? Procedure #2 from the thread below... Seems to work everytime...
[How to] Factory Restore (or Fix a Bricked Phone)

Thanks, I got up to here but then ODIN failed

<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> param.lfs
<ID:0/007> Sbl.bin
<ID:0/007> boot.bin
<ID:0/007> recovery.bin
<ID:0/007> zImage
<ID:0/007> factoryfs.rfs
<ID:0/007> datafs.rfs
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)


I unplugged the phone. The Samsung Mobile Screen and part of the Sprint Splash screen have returned. Then it loops back into the Samsung Mobile screen constantly until I pull the battery (this is probably because the thing failed.). I'm gonna try it again. I am lucky enough to have a back-up of my phone back on EH17 right before I did all of this. Is it possible for me to just flash that?
 
Thanks, I got up to here but then ODIN failed

<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> param.lfs
<ID:0/007> Sbl.bin
<ID:0/007> boot.bin
<ID:0/007> recovery.bin
<ID:0/007> zImage
<ID:0/007> factoryfs.rfs
<ID:0/007> datafs.rfs
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)


I unplugged the phone. The Samsung Mobile Screen and part of the Sprint Splash screen have returned. Then it loops back into the Samsung Mobile screen constantly until I pull the battery (this is probably because the thing failed.). I'm gonna try it again. I am lucky enough to have a back-up of my phone back on EH17 right before I did all of this. Is it possible for me to just flash that?
You could try your backup in CWM but seeing how its still hanging up it may not work... Worth a shot but just incase read further..

Use that Procedure #2 again this time run the whole thing with your battery out of your device... Dump the battery and hook up and boot into Download Mode and see what happens.. Don't forget to reboot your computer too so thats cleared out from previous Odin attempt. If it all works and you get the Green Pass then pop your battery back into your device and unplug and reboot.

Report back.. Good luck.
 
You could try your backup in CWM but seeing how its still hanging up it may not work... Worth a shot but just incase read further..

Use that Procedure #2 again this time run the whole thing with your battery out of your device... Dump the battery and hook up and boot into Download Mode and see what happens.. Don't forget to reboot your computer too so thats cleared out from previous Odin attempt. If it all works and you get the Green Pass then pop your battery back into your device and unplug and reboot.

Report back.. Good luck.

Thank you so much for your help. I'm gonna try this stuff now.

Edit: I tried what you said (procedure 2) and this happened:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D700-EB13-8Gb-REL.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> param.lfs
<ID:0/008> Sbl.bin
<ID:0/008> boot.bin
<ID:0/008> recovery.bin
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)


it failed after recovery.bin. The CWM didn't work either. Anything else I could do?
 
Last edited:
Try a different USB cable or port on your computer. I know I have a couple of cables that Odin just doesn't like.

I had this same issue one time when trying to return my phone back to stock and I had to use the appropriate pit file and the appropriate tar file to get it to work.

Can't remember which pit file I used though whether it was the victory8g pit or the s1_odin pit.

Also which version of odin are you using. I tried to use 1.81 and couldn't get it to go back, so used 1.61 and it worked.
 
Last edited:
Good suggestions above... Also you can pull your sdcard that has worked for some.. Why? dunno..

Turn off any anti virus on your computer while doing the Odin process...

Different ports/cables... Normally rear of computer is best, nearest to motherboard... Laptops, try each one.... Laptops make sure they are plugged in so your getting maximum juice to the USB ports....

Heck at this point even try going back to Eclair 2.1 DI18 and see if that works... That is procedure #3, if I remember correctly.... We can work from there too:)
 
ive been using different ODINs, 1.6, 1.8 mostly. ive tried different pit files, with and without sd card and battery, different ROMs DI18, Eb13, EC05, EH06 and EH17, and different usb ports. i got close using a different usb port. but ill try disabling antivirus.

thanks to you both, if you have any other ideas please send them my way.
 
ive been using different ODINs, 1.6, 1.8 mostly. ive tried different pit files, with and without sd card and battery, different ROMs DI18, Eb13, EC05, EH06 and EH17, and different usb ports. i got close using a different usb port. but ill try disabling antivirus.

thanks to you both, if you have any other ideas please send them my way.

Didn't hear you say you have used a different cable? I know they are not easy to come by at a pinch but radio shack or a good computer electronics store will have em.... Not the cheapest but they do...

I've seen a bad cable stop the installation like your having problems with... It gets so far and then haults.. Charges the phone excellent too but won't complete an Odin job
 
Didn't hear you say you have used a different cable? I know they are not easy to come by at a pinch but radio shack or a good computer electronics store will have em.... Not the cheapest but they do...

I've seen a bad cable stop the installation like your having problems with... It gets so far and then haults.. Charges the phone excellent too but won't complete an Odin job

I'll try and look for another one.

Edit:Went out and found another one. It's not Samsung, it fits but isn't recognised by Odin.
 
Last edited:
If you haven't gotten it working try this.

Use Odin 1.6 and have just repartition selected and only do the s1_odin pit file.

After that is done, reboot your computer and your phone, put your phone back into download mode and then try using the tar file to restore back to stock using the info in the other thread.

I had a similar problem and I remembered what it was that I did to finally get it to work.
 
Even this did not work, and sadly the phone is bricked entirely. I'm being sent a new one, thanks for everyone's help anyways.
 

Trending Posts

Forum statistics

Threads
956,569
Messages
6,968,866
Members
3,163,566
Latest member
SmoothieP