Database Develop

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

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!!!

nin2thevoid said:
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!!!
Click to expand...
Click to collapse
Flash some ecleir ROM with 512 re-partition. Hope this helps.

ragin said:
Flash some ecleir ROM with 512 re-partition. Hope this helps.
Click to expand...
Click to collapse
Try the Odin 1.7 from my thread posted here.

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..

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!

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

nin2thevoid said:
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!
Click to expand...
Click to collapse
If it has helped you, please post a reply in my thread. can help others like you.

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.

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!!

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

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!

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 !!

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!

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

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...

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!

[Q] Trouble restoring 2e recovery on GT-I9000 using odin

firmware - 2.2.1 (Froyo)
Baseband - I9000XXJPY
Current Kernel version - 2.6.32.9
using windows 7
I rooted my phone, but obviously can't flash cwm because I have the 3e recovery.
My phone is in download mode, usb debugging mode.
I've made sure the drivers are installed and kies is completely removed from my computer.
I open up odin (keys isn't running, the pc recognises it), and odin recognises the phone
Re-partition is unchecked, and I've tried using both CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.15.3 and CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.17.1 as the pda types.
However I click start and it gives me
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Not sure where I'm going wrong, can someone help me please?
(sorry, I'm sure this is a question that's commonly asked, but I've searched other threads and haven't found anything that's solved my problem)

it could be a bad download..
i would say the easiest way is download speedmod kernel (odin version)
flash that, if will give you CWM recovery and a lot of other tweaks too, if you dont like it, you have CWM to flash another kernel / rom in recovery...
simple and safe

Alright, I just realised how much of an idiot I really am... I was holding down the button combo for download mode until it went back out of download mode, rather than connecting the usb whilst it was showing the download mode screen
Not sure how I misread that step in every single faq =|
Thank you very much for taking the time to reply though

[Q] Stuck in Odin when flashing kernel

I was following the overcome guide and when i came to step 8/9 (flash overcome kernel) it didn't work, so then i chose the same pit which you use in a previous step and also the kernel and now it worked with the pit but not the kernel. i got stuck in download mode and tried to flash only kernel again but it didn't work not it got stuck on ConnectionSetup... or something like that. I think it couldn't find the device, i shut down odin and took out the micro-sd card which someone said could cause problems but it still didn't work. now i'm stuck at a screen like this: picture of phone .. ! .. picture of computer. I guess it means it can't connect to the computer. Anyone know what to do? I've tried searching the forums and tried some different stuff but haven't succeded.
Edit: Seems like i can use odin even though i don't get into the download mode, will update soon. Seems to work correctly, i'll give the flashing another try and i will make sure to cross the right boxes and so on.
Edit2: This time i checked that i had all the correct things crossed in Odin but when i try to flash the kernel it fails. what should i do? i come from gingerbread 2.3.3 (re-stocked) so it can't be the bootloader right?
Edit3: This is what i get when i try to flash the kernel:
<ID:0/036> Added!!
<ID:0/036> Odin v.3 engine (ID:36)..
<ID:0/036> File analysis..
<ID:0/036> SetupConnection..
<ID:0/036> Initialzation..
<ID:0/036> Get PIT for mapping..
<ID:0/036> Firmware update start..
<ID:0/036> ‹
<ID:0/036> NAND Write Start!!
<ID:0/036>
<ID:0/036> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Edit4: From my research it seems i have the same problem as people hade with the signed/locked bootloaders on froyo, however i'm running 2.3.3 and the thread specifically said not to use their patch so i have no idea of how to solve this. Help would be very appreciated.
Edit5: finally works, thanks to this: http://forum.xda-developers.com/showthread.php?t=1324052

Galaxy S I9000M - keep rebooting (software brick)

Hi,
I managed to brick my Samsung Galaxy S I9000M.
Was locked on Virgin network (Canada) and I was trying to root the phone and then unlock it.
But something didn;t work properly (or I made a mistake) and now the phone keeps rebooting. I can go into Download mode but nothing more.
This is what I did:
1) I installed Odin 1.85
2) I started ODIN as admin, I pressed on PDA and then I selected a zip folder called
"CF-Root-XX_OXA_JVO-v3.2-CWM3RFS"
3) This is what ODIN was showing:
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
5) So after waiting 5-6 minutes (in this time the phone was rebooting up to the Samsung logo) I turned off the phone and I have tried to start the device. But is not starting anymore, it keeps rebooing.
Now I don't know what to do to fix it.I know that I made a big mistake, I was not supposed to do something without knowing what I'm doing...But now it's too late, I have to fix it.
Note: The phone was running Android 2.3 (Gingerbread)

if its in boot loop then look like it's only softwoer brick.
so if you can get in to download mode by 3 bouten combination greate you can try to reflash (I will try all so to redownloading the files)
if not than you must find a JIG or some one with a JIG to get in to download mode and reflash.

The version of CF-ROOT you selected is not compatible with the version of GB (UGKG3?) that was on your phone.
If your phone had UGKG3 installed, there are very few rooted kernels available for it.

Black Rose said:
The version of CF-ROOT you selected is not compatible with the version of GB (UGKG3?) that was on your phone.
If your phone had UGKG3 installed, there are very few rooted kernels available for it.
Click to expand...
Click to collapse
Is the latest speed mod kernel compatible?
Sent from my GT-I9000 using xda premium

Yes, I can go into download mode.
How can I reflash the phone ? Which kernel should I use ?
Sorry but I'm new in this.
If you give me some links that will be great.
I don't want to aggravate the situation .

If the OP has/had UGKG3 installed, I have found that to be the oddest ROM I have used to date on my phone.
It does a lot of things differently.
I made another post on here where I attached a basic rooted kernel for the UGKG3 ROM. Let me go find it and link to it.
Again, this is assuming it was UGKG3. Ma Bell has only released one GB ROM for the GT-i9000m, so I think it's a safe bet that's what the OP was running on his Virgin branded phone.
EDIT: Here it is: http://forum.xda-developers.com/showpost.php?p=21655532&postcount=492
This will give you a basic rooted kernel, no CWM or anything else, just root.
You'll also need to download Superuser from the Market.

Thank you.
Now how should I install that kernel?
I suppose that after I reflash the phone it will start normally and then I can go to the Android market and install Superuser from there?
Is there a link with instructions (Step by Step guide)?
Sorry,but I dont have too much experience with this.
Thanks a lot!

I found this in the General thread, it has links and step-by-step instructions:
http://forum.xda-developers.com/showthread.php?t=1379650
Hope it helps

IntelQC said:
Thank you.
Now how should I install that kernel?
I suppose that after I reflash the phone it will start normally and then I can go to the Android market and install Superuser from there?
Is there a link with instructions (Step by Step guide)?
Sorry,but I dont have too much experience with this.
Thanks a lot!
Click to expand...
Click to collapse
Open Odin, select the zImage.tar file as PDA. DO NOT CHANGE ANY OTHER SETTINGS.
Connect your phone to your computer and wait for the ID:COM box to turn yellow.
Press Start.
Your phone will reboot and it should start normally.

Black Rose said:
Open Odin, select the zImage.tar file as PDA. DO NOT CHANGE ANY OTHER SETTINGS.
Connect your phone to your computer and wait for the ID:COM box to turn yellow.
Press Start.
Your phone will reboot and it should start normally.
Click to expand...
Click to collapse
Thank you very much !!!
My phone is fine now. It's rooted and I managed to unlock it using Galaxy_S Unlock + SuperBox from the market.
Thanks a lot .
This is what my phone shows now:
Firmware: 2.3.3
Baseband version: I9000UGKG3
Kernel version: [email protected]#2
Build number: GINGERBREAD.GKG3

Great, glad you got your phone working again.

[Q] Complete(Write) operation failed - on Odin when trying to revert from Cmod

Hello, I am trying to get rid of Cyanogem mod because many apps don't work (Netflix ) but it's giving me this error everytime.
Code:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It no longer boots at this point, but still shows cyanogem mod logo.
I can still acess Clockwork recovery
Kies drivers updated
Original usb cable, tried changing ports too
Odin set up correctly, version 3.09
Still able to get download mode done
I have tried everything i could find on google, still nothing, i'm really getting worried here
Phone screen on download mode :
ODIN MODE
PRODUCT NAME: GT-I8190L
CUSTOM BINARY DOWNLOAD : YES(4 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CUSTOM Modem BINARY !!
HW REV: 0X5
thanks in advance

ppgab said:
Hello, I am trying to get rid of Cyanogem mod because many apps don't work (Netflix ) but it's giving me this error everytime.
Code:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It no longer boots at this point, but still shows cyanogem mod logo.
Kies drivers updates
Original usb cable, tried changing ports too
Odin set up correctly, version 3.09
Still able to get download mode one
I have tried everything i could find on google, still nothing, i'm really getting worried here
thanks in advance
Click to expand...
Click to collapse
You must download the original rom from SamMobile, install it through Odin 3.0.7 and reboot. Then install again through Odin the Recovery and through Recovery your new Rom. :good:

Open task manager on your computer and make sure that nothing with kies is running.
If you're on f2fs you can also try to format system, cache, data back to ext4 from recovery before using Odin.

tys0n said:
Open task manager on your computer and make sure that nothing with kies is running.
If you're on f2fs you can also try to format system, cache, data back to ext4 from recovery before using Odin.
Click to expand...
Click to collapse
You mean format using clockwork recovery? i dont know much about this subject
Do you know if i can install trough external sd using cw recovery mod?

ppgab said:
You mean format using clockwork recovery? i dont know much about this subject
Do you know if i can install trough external sd using cw recovery mod?
Click to expand...
Click to collapse
Yes. If you're on cm from Novafusion the system partition is on f2fs by default. Not sure of how Odin likes that.
If you mean install zips from external, then yes you can.

tys0n said:
Yes. If you're on cm from Novafusion the system partition is on f2fs by default. Not sure of how Odin likes that.
If you mean install zips from external, then yes you can.
Click to expand...
Click to collapse
edit: the issue was Odin 3.09, i downloaded 3.07 as the guy said above and it worked ^^
thank you all for the time
This thread can be closed/Solved.