I was running Webstar's "Ultimate" ROM 3.0, after which I decided to go to stock and then upgrade to a different ROM.
I flashed stock 2.2 stock firmware with Odin 1.7 with 803 pit (from samfirmware.com). Now my phone is stuck on a black screen and vibrates after the Samsung boot animation.
I had disabled the lagfixes and tweaks from recovery but the files still stayed back on the sdcard.
This is what Odin says :
<ID:0/023> Added!!
<ID:0/023> Odin v.3 engine (ID:23)..
<ID:0/023> File analysis..
<ID:0/023> SetupConnection..
<ID:0/023> Initialzation..
<ID:0/023> Get PIT for mapping..
<ID:0/023> Firmware update start..
<ID:0/023> cache.rfs
<ID:0/023> factoryfs.rfs
<ID:0/023> modem.bin
<ID:0/023> param.lfs
<ID:0/023> zImage
<ID:0/023> Removed!!
<ID:0/023> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Recovery mode/Download mode works for me. I tried clearing cache/factory reset, it worked, but my phone's still stuck on black screen.
I tried reading through similar threads on the forum, but most of that hasn't helped me. I also get the yellow screen something like -----|---- (which I haven't tried with Kies)
I'm downloading the 2.1 stock firmware now, I will try flashing it with Odin.
I just got this phone last week so I deserve to panic a little :\
Same issue with my friend phone
she said was playing with apps in the markets then crash
then Black screen after the Big S show.
Tried wiping cache and data, not working
Flash it with stock 2.1, not working ~
stucking and need assistance
video of booting
I tried 2.1 firmware without PDA and Re Partition on Odin, still doesn't work.. It says successful but stuck at black screen post reboot.
Edit: *Finally works*
I did an odin flash with 512 pit, with repartition selected. After boot format sd/factory reset and clear cache. REMOVE USB, and reboot.
Hope this works for her.
killslayer said:
I tried 2.1 firmware without PDA and Re Partition on Odin, still doesn't work.. It says successful but stuck at black screen post reboot.
Edit: *Finally works*
I did an odin flash with 512 pit, with repartition selected. After boot format sd/factory reset and clear cache. REMOVE USB, and reboot.
Hope this works for her.
Click to expand...
Click to collapse
mind finding the exact link for the Odin and Pit and Firmware for me ?
i wanna try to exactly the same thing, hopefully will work for her too
wildbat000 said:
mind finding the exact link for the Odin and Pit and Firmware for me ?
i wanna try to exactly the same thing, hopefully will work for her too
Click to expand...
Click to collapse
Sorry I dont have the links anymore, you'll have to look around a bit. I got the firmware from samfirmware.com
You can get the firmware for your area there and search for odin 1.7 with pit files, shouldn't be hard.
Still stucked
anyone know a fix
got Download mode and Recovery Mode
but just won't boot up .... (as shown in the video)
anyone have a clue?
Flash an old Eclair firmware that uses 512.pit. (In fact, all of them should.) Get them off www.samfirmware.com
did it many times~ not working
Related
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!
Hi
I was trying to flash another ROM on my SGS, while having some bugs on CM7.
I formatted system, cahce and data, and did wipe data/factory reset + wipe cache.
I kept getting an error on flashing the new ROM, and accidently hit the "reboot system" while navigating around in CWM3.0.0.5. Now I can't get back to CWM with 3-button combo and got no ROM on my phone?
what to do? Wierd enough I can get into download mode
thanks in advance
PS: I normally use 3 button combo to get into CWM, and did this prior this episode
just flash via odin, with 3 files and re-partition.
that should work.
derrzredeem said:
just flash via odin, with 3 files and re-partition.
that should work.
Click to expand...
Click to collapse
I'm not so farmiliar with Odin yet... tried it a couple of times, sticking strictly to a guide, that I cant find right now :S
Could you give me a quick tutorial in what to combinate .e.g.?
PIT? PDA? PHONE or CSC? And what is what?
I know I used to flash a radio with the PDA function...
thanks
you should flash a low level package means a 3 files PDA, MODEM and CSC.
i.e XXJPU which contains XXJPU_modem, OXAJPU_CSC, and XXJPU_Rev3_PDA. Now you should put the files according to the names (like PDA in PDA, Modem in Modem and so on). I usually use 512pit for re-partition.
You should not put modem in pda when flashing using odin, like i said before "put the files according to the names"
ps. Do not tick any other option except repartition, (F. Reset Time, and Auto-reboot) when going back to samsung ROM from CM7
Good Luck
derrzredeem said:
you should flash a low level package means a 3 files PDA, MODEM and CSC.
i.e XXJPU which contains XXJPU_modem, OXAJPU_CSC, and XXJPU_Rev3_PDA. Now you should put the files according to the names (like PDA in PDA, Modem in Modem and so on). I usually use 512pit for re-partition.
You should not put modem in pda when flashing using odin, like i said before "put the files according to the names"
ps. Do not tick any other option except repartition, (F. Reset Time, and Auto-reboot) when going back to samsung ROM from CM7
Good Luck
Click to expand...
Click to collapse
Thanks a lot. You just managed to answer my next question at the same time as I was about to put it out (regarding check marks F. Reset Time, and Auto-reboot)... looks like it is going through now... The blue line is increasing anyway under the litthe android builder
thank you so very much
EDIT: God dang it Phone bootet up once again in original rooted firmware anf 3e recovery is back
Hmm... seems I was a bit to fast on the keyboard anyway
Followed "How to: flash firmware and kernels" from post #2 in this thread
http://forum.xda-developers.com/showthread.php?t=723596
I found a 512 pit from the link, where I also downloaded Odin. I chose the I9000XWJS3.7z from original firmware package (from the link), which included a .tar file, that I chose as PDA.
The phone boots up now, but when as it is about to show android UI, it starts to vibrate and the screen turns black, and menu button + back button light up continously.
I can get into 3e recovery know though, but is there a way to flash clockworkmod or another custom recovery via odin og 3e recovery? or could I try another combination of pit and PDA file ind Odin?
thanks again
Odin log:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> modem.bin
<ID:0/004> param.lfs
<ID:0/004> zImage
<ID:0/004> cache.rfs
<ID:0/004> factoryfs.rfs
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
You're in a bootloop. Try wipe cache partition and do a factory reset from recovery and then reboot.
If that doesn't work try a different firmware. A LOW LEVEL PACKAGE one, JPU for example.
Afaik, JS3 only had one file (and the new JS3 is using 803pit file, tho it comes with 3 files; for me 512 always gave the best result).
Edit : You need to use a correct pit file when flashing a firmware.
~drz
derrzredeem said:
You're in a bootloop. Try wipe cache partition and do a factory reset from recovery and then reboot.
If that doesn't work try a different firmware. A LOW LEVEL PACKAGE one, JPU for example.
Afaik, JS3 only had one file (and the new JS3 is using 803pit file, tho it comes with 3 files; for me 512 always gave the best result).
~drz
Click to expand...
Click to collapse
Just to make sure I got the last part right. 803pit is for JS3? but I can use 512pit instead?
where do I get 803pit? do you have a link?
Im downloading JPY and will test it, if 803pit og wipe doesn't work.
thanks for the response
larsn84 said:
Just to make sure I got the last part right. 803pit is for JS3? but I can use 512pit instead?
where do I get 803pit? do you have a link?
Im downloading JPY and will test it, if 803pit og wipe doesn't work.
thanks for the response
Click to expand...
Click to collapse
God, you need to learn to listen/read. Use JPU, JPY is a single file.
Ps. Good luck though
~drz
Okay, I thought the name JPU/JPY determined which area it is fore?
Im downloading from here
https://www.wuala.com/Samsung Galaxy S/Firewares , Updates and Odin/?key=AfzUZSU4SpKU
but I cant seem to find JPU...
thanks for your help. Im a bit noobish regarding samsung... Its buy far not the same as HTC hehe
EDIT: Can't I just flash an original firmware with Odin, and it such case? Where do I find it. tried JPY, JS3 from above link, and get bootloops no matter what. Those files are downloaded from the sticky guide in general section, and I followed the guide. If I need to use JPU, where do I download it? all 3 files?
Right now, the phone just vibrates in intervals, but contiounsly, with back button and menu button light on
Yes, every firmware is for different region. But you need to get your phone to work first, right?
After that you can flash any firmware you want
You can download JPU from http://samfirmware.com or find a thread by BogdanSNB in general section.
Btw, Gingerbread is out
~drz
SOLVED
Finally got it to work with XJWM9 as PDA, XEEJM1 as CSC, XXJM4 as PHONE and 512pit file.
Hi,
I Semi Bricked my SGS I9000 and need an advice what to flash now.
I am on Gingerbread for around 2 weeks now. Went from JVH to JVO today.
Here is what i did:
- Flashed JVO (as usual, deodexed without bootloaders from here) with ODIN with Pit and Repart
- booted the Phone without issues, copied some stuff from my PC over to the phone
- rebooted into Download, tried to Flash the latest CF Kernel (CF-Root-XX_OXA_JVO-v3.2-CWM3RFS)
Odin (v. 1.7 on Windows 7 64bit btw) had an issue with it:
<ID:0/014> Added!!
<ID:0/014> Odin v.3 engine (ID:14)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> zImage
<ID:0/014> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/014> Removed!!
After that my phone wont boot, only shows the symbol with the red ! and the Android Logo.
Download Mode is working.
What to do now?
Should i flash the JVO (deodexed, without Bootloaders, with Pit and Repart) from the Link above? Or do i have to flash a Stock JVO (with Bootloaders) from Samsfirmware with Pit and Repart?
Or do i need to do anything else?
Greetings
the symbol appears when your bootloader is trashed.
flash again with bootloaders and it will work on most cases
http://sourceforge.net/projects/teamhacksung/files/galaxys/GT-I9000_FROYO_FULL_PDA.tar/download
firstly i would flash the above firmware
if that does not fix it, i suggest flashing (cant believe im saying this) darkys 9.2 odin version with 512 pit and re-partition. and THEN re-flash the above firmware
That should get you to a clean stable state, and you can decide where to go from there, i.e back to GB or custom ROM, whatever
Could anyone explain why I have to go back to Froyo when my Phone is running Gingerbread?
I still have a JPU with Bootloaders lying around here.
So the way back to a working phone would be
1. Flash JPU with Bootloaders, Pit and Repart
2. Flash JVB with Bootloaders, Pit and Repart
3. Flash JVO, without Bootloaders, without Pit and Repart
Another question is:
Did i do anything wrong, regarding my JVO and CF Version? I flashed around a lot today.. and i am... 70% sure that i flashed that combo today successfully, but there are the missing 30% ^^
oh yea i misunderstood your last post,
if your on GB now flashing GB bootloaders might fix you up, BUT if it doesnt, a clean install back to froyo always seems to do the trick for me
So, i will only do this:
2. Flash JVB with Bootloaders, Pit and Repart
3. Flash JVO, without Bootloaders, without Pit and Repart
(leaving out 1.)
?
yes, then report back with the outcome.
good luck
Got the phone up and running again with JVB + Bootloader + 512-pit + repart
Used this:
http://www.multiupload.com/ZYSFTX1DV9
And this:
http://www.multiupload.com/OAJ00SWTF1
If anyone happens to need that too.
Flashed JVO, deodexed and CF Kernel without issues now - but i used Odin 1.3 this time..
congratulations
good to hear you back up and running.. Perhaps you could put [SOLVED] in the title ?? may help other users with similar issues.
Hey guys i have followed the guides , i was putting on a stock rom for my phone to be sent back as a replacement. it failed half way through the flash when i upgraded the phone to 2.2
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.rfs
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can get back into recovery mode. I tried flashing it with the PIT PDA and CSC file. It fails constantly, i clicked re partition in one flash too it didnt work either. SO i am stuck. Any other suggestions?
Using odin 1.3 - It worked the multiple other times i flash it to different roms.
Maybe you're using Windows x64? try using another version of Odin, possibly 1.7 & make sure when you open it to go to the correct pit file & not the last one opened, also if the phone is going back do a wipe/factory rest too in recovery mode & then try reflashing with Odin, hope that helps.
Hi i used a windows XP machine with the same results. I did try 1.3 and 1.7.
is there another PIT file i can try? I downloaded a couple and neither worked.
I have no recovery anymore only download mode, the phone does not boot at all no phone -> computer icon.
Is the 512 PIT file the right one for the galaxy thought it was.
Have you tried redownloading the firmware? Or another source for the same firmware? Maybe its corrupt somehow. I know it is supposed to check the md5 but worth a shot. Or try an earlier version of your firmware, if it is for return they shouldn't care.
G
I have tried 3 - 4 different roms with all the same result, the phone was going back under a different issue (network related). It always fails at the same point from each rom.
Steps i have done.
1. pit file only (repartition)
2. pit pda and csc (512 pit , vodaAU stock rom, voda au csc)
3. standard stock rom (which worked) but doesnt now.
4. Darkys resurrection rom (failed same spot)
5. odin 1.3 and odin 1.7
6. windows 7 and windows XP
I am annoyed about this, the other times worked fine! Just went i went to send it back for replacement . boom failed.
I tried a more recent ginger rom, failed again act factory.rfs. It's almost like the internal SDcard is broken. This time it flashed modem.bin
Did you remember to turn off the lagfix before the first flash? If the file system is ext4 and you flash RFS then I think that you can have issues.
There is a way to fix it as I was on another thread today where that was the issue but I don't know if the error showed up in Odin for them.
Just another thought...
G
BTW I think in most cases odin will still flash OK even if SD card is cooked. We i9000m owners know way too much about that...
After google search you also might try 1) another odin or heimdall - personally I'd try heimdall at this point if I were you or EZ odin maybe? 2) You likely know not to have kies agent in the tray but hey worth mentioning 3)redownload drivers (which I'll guess that you've done too)
Hi mate ,
Yes i did disable lag fix before flash i kept the orig rfs file system did not convert to EXT4. I might try Heimdall.
After google search you also might try 1) another odin or heimdall - personally I'd try heimdall at this point if I were you or EZ odin maybe?
2) You likely know not to have kies agent in the tray but hey worth mentioning
All taskmanager escaped all the kies stuff, reinstalled kies as well.
3)redownload drivers (which I'll guess that you've done too)
Did this on two machines.
EZ odin fixed it. It booted i just put my providers CSC on it, im pretty sure they wont check the base band and rev number when they get it back.
Glad it worked!
G
Sent from my GT-I9000M using XDA Premium App
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