[Q] [SOLVED!] USE ODIN >1.7 (semi?) bricked ... despite precautions galaxy s odin

[nin2thevoid]

Hey guys,

First of all I checked every brick thread I could find and I am pretty sure none of the solutions applies to my problem.

I've flashed hundreds of times on numerous phones so I take most precautions to make sure I don't brick my phone, still, that's what happened now for the first time.

Situation:

- Download mode and recovery mode checked... both working
- Had Darky's DarkSteel 3.0 running with LagFix (no problems)
- Disabled LagFix by adding the folder
- Reboot ... disabled lagfix ... still running strong
- Flashed Darky's LegendarySteel 4.0 ... running
- Reboot ... hey no Voodoo ... oops lagfix folder was still there of course
- removed folder
- reboot ... still no lagfix ... OK so I accidentally chose the wrong Darky's ... The one with SpeedFix kernel not the one with Voodoo
- remember: lagfix folder still there, but I thought it would not be enabled as Darky's SpeedFix version had no Voodoo, also, Quadrant showed 900 like you would expect without lagfix
- Checked recovery/download just for precaution ... both working still
- Flashed the rom I wanted: Darky's LegendarySteel 4.0 with VOODOO
- So basically, I flashed WITHOUT "disable lagfix" folder, somehow thinking this would not be a problem considering LagFix wasn't running on the previous rom, and was disabled before flashing the previous rom.
- Clockwork Recovery clear cache / wipe partition ... choose zip ... run update ... OK REBOOT
- Stuck at Galaxy S logo
- No recovery
- Download mode works
- Tried Odin to flash stock rom using PIT 512 with and without repartition ... both just wait for a long time on some message "checking file system" and I don't know how long that should take but after 20mins I gave up.
- Tried rebooting and waiting forever as advised on the Voodoo site ("if you had a lagfix enabled previously, it will take forever, just be patient") well I waited forever (hours?) and still "Galaxy S" bootup screen

- Kies recognizes nothing
- Same for ADB
- Only download mode works ... Odin does recognize the device so all could not be lost right?

My questions:
- What should I flash (including firmware, PIT, odin version, repartition, wait time etc) to get up and running again?

Any help would be greatly appreciated!!!

 

[ragin]

Hey guys,

First of all I checked every brick thread I could find and I am pretty sure none of the solutions applies to my problem.

I've flashed hundreds of times on numerous phones so I take most precautions to make sure I don't brick my phone, still, that's what happened now for the first time.

Situation:

- Download mode and recovery mode checked... both working
- Had Darky's DarkSteel 3.0 running with LagFix (no problems)
- Disabled LagFix by adding the folder
- Reboot ... disabled lagfix ... still running strong
- Flashed Darky's LegendarySteel 4.0 ... running
- Reboot ... hey no Voodoo ... oops lagfix folder was still there of course
- removed folder
- reboot ... still no lagfix ... OK so I accidentally chose the wrong Darky's ... The one with SpeedFix kernel not the one with Voodoo
- remember: lagfix folder still there, but I thought it would not be enabled as Darky's SpeedFix version had no Voodoo, also, Quadrant showed 900 like you would expect without lagfix
- Checked recovery/download just for precaution ... both working still
- Flashed the rom I wanted: Darky's LegendarySteel 4.0 with VOODOO
- So basically, I flashed WITHOUT "disable lagfix" folder, somehow thinking this would not be a problem considering LagFix wasn't running on the previous rom, and was disabled before flashing the previous rom.
- Clockwork Recovery clear cache / wipe partition ... choose zip ... run update ... OK REBOOT
- Stuck at Galaxy S logo
- No recovery
- Download mode works
- Tried Odin to flash stock rom using PIT 512 with and without repartition ... both just wait for a long time on some message "checking file system" and I don't know how long that should take but after 20mins I gave up.
- Tried rebooting and waiting forever as advised on the Voodoo site ("if you had a lagfix enabled previously, it will take forever, just be patient") well I waited forever (hours?) and still "Galaxy S" bootup screen

- Kies recognizes nothing
- Same for ADB
- Only download mode works ... Odin does recognize the device so all could not be lost right?

My questions:
- What should I flash (including firmware, PIT, odin version, repartition, wait time etc) to get up and running again?

Any help would be greatly appreciated!!!

Flash some ecleir ROM with 512 re-partition. Hope this helps.

 

[ragin]

Flash some ecleir ROM with 512 re-partition. Hope this helps.

Try the Odin 1.7 from my thread posted here.

 

[st4rk]

Try flashing back to the kernal that you had on the rom first?

Don't really know if it would help.. just taking a shot in the dark..

 

[nin2thevoid]

God I love this forum. Thanks for the tips all. I was using older ODIN and now using 1.7 (couldn't find it in the specified thread since the link was missing ^^ but used the forum search instead).

It's flashing ... At least that!! I will report back how it goes!

Edit:

<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> dbdata.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> param.lfs
<ID:0/003> modem.bin
<ID:0/003> cache.rfs
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)

Live and kicking again! Woot... Thanks all!

 

[dupel]

Well, atleast we know that odin 1.7 is more stable and more "unbrick" friendly =)

 

[ragin]

God I love this forum. Thanks for the tips all. I was using older ODIN and now using 1.7 (couldn't find it in the specified thread since the link was missing ^^ but used the forum search instead).

It's flashing ... At least that!! I will report back how it goes!

Edit:

<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> dbdata.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> param.lfs
<ID:0/003> modem.bin
<ID:0/003> cache.rfs
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)

Live and kicking again! Woot... Thanks all!

If it has helped you, please post a reply in my thread. can help others like you.

 

[mike.sw]

from my experience odin works the best if you connect your phone and hit the flash button immediately. connecting the phone in download mode and waiting with it always caused the flash process to "stuck" just like you describe.

anyway happy 1.7 helped you.

 

[derbysig]

I had the exact same problem last night.
to solve the issue... I basically reflashed to ECLAIR JM8.
Then installed the ROM i wanted from clockwork recovery, and everything went back to normal!

Hope things work out well for you! cheers!!

 

[d1dd1]

I guess Re-Partition solved the problem. This should also work with Odin 1.0 / 1.3

 

[nin2thevoid]

No it was 1.7 that solved it since I did the exact same steps as with 1.3. Upgrading Odin was the fix for sure. I'm surprised not many people use 1.7... all the tutorials and guides point to 1.0 and 1.3.

Thanks for all the help guys!

 

[mvmw]

hi gays,
actuly i have the same problem " screen of death "
but it happened whit my when i tried to flash -speedmod kernel - and - ce-root- in PDA
and it's stopped in middel of the action -- it happened in odin3 1.7 > it's naver happened in odin3 1.3 and odin3 1.3.2
i think there something wrong with 1.7
--sorry for bad English - i hope you understand what i'm tring to say
thanks for your time !!

 

[Sparkle1975]

I have a similar problem, which is not solved yet. I would be glad if someone would help.

Explanation of my probs:
I think I've bricked my SGS. It's a European version, not branded with T-mobile or any operator.

Friday I flashed the JPU (Android 2.2.1) and it worked fine. I've updated it several times via Odin, and never really had problems.

Then I installed the Voodoo recovery image and a custom ROM (Darkys 5.2 ROM). Still worked fine, a quadrant score of 1650. But then... I went to the recovery and chose to partition the internal SD card (EXT3/4). The phone said it succeeded doing this, but then it rebooted and I only got the Samsung logo (in white, no colors). Waited for 10 minutes, nothing happened.

Now I can't get it into recovery mode, however, the 3-button combo is still working, so I can get it into download mode as usual. But it does'nt work. It starts, I get the green slider on the phone, but after a very short time the update stops, it happends while Odin writes sbl.bin

I've tried several ROM's, but it does not work. I don't know what to do now - why can't I flash the phone even though it's in download mode?

Hope that someone can help me.

--- update ---
Hmm, maybe I'm on the right track now - I hope so.

Now I can turn on the phone, but it does go into the stock recovery, even though I just turn it on. It's the stock recovery (Android system recovery <2e> Samsung recovery Utils - for BML -

I downloaded Odin 1.7 from this link:
Download Odin-1.7with.pit.512.803.zip from General-Search.com

I did this on my work computer instead of my laptop. Never used Odin on this computer before. Then I just wanted to test Odin, so I chose some random PDA file I had on the computer. I chose the JPK Root + Busybox 1.17.1 + 2e\i9000_Kernel.tar that I used for rooting the JPK firmware when I was running that.

Then I have flashed the other file from that package (I9000XXJPK_Kernel.tar) - but when I turn on the phone, it stops but shows the white Galaxy S logo.

...more to come.

UPDATE!

UPDATE! Flashed JM7 firmware (that's the newest I already had downloaded on my work computer) and the beast is ALIVE AGAIN! Hallelujah!

 

[buba007]

I solved it with old ODIN flash 1.3 firmware JPA_JP4_U_JPP.tar (no pit file) USB pluged and unpluged a cuple of times. no repartition and no bootblock . After first flash i had to wipe and factery restore in 2e recovery. and flash again. After that the phone was fine. The KIES version i have installed is 1.5.3.10103.102. I think it is the driver version that KIES installs that is the problem, You could try installing older KIES vith older drivers. After first flash the new firmware could not install aps after first boot, thats why i wiped and flashed again.
Sory for bad English

 

[qingren]

Help pls.. I can run but it failed in the end after waiting it to run. I had tried reopening the oldin and replug in batt all no use...

 

[Armada3000]

Thank you so much for the tips here guys, been trying to recover my nephews softbricked i9000 for 5 days now - finally sorted, woohoo!!!!


I used Odin 1.7, Re-Partitioned with the 512 pit file and flashed a stock rom.
This was my last attempt too so Christmas has come early!