Database Develop

Stuck after bad rom flash, odin wont recognize

So heres the synopsis on what my issue is:
first of all-
phone: Samsung Captivate build 1010
current OS: (botched install of Darky 8)
problem: no recovery menu capability, stuck in reboot loop (will not go past ATT Logo), can go into download mode but odin does not see the phone
I botched a Darky 8 install. I attempted to install the rom to my captivate via rom manager but to no avail. I then decided to give the install a try via clockwork and had luck. the rom was not to my liking so I went to mount the internal sd and proceeded to delete all files internally to make a fresh odin install possible (as I always do). It was at the time of restarting my phone that I realized the rom I install was accidently the I9000 rom on my captivate, thus forth being a possible source of my issue. Currently I have a phone that is stuck in a reboot loop any time I plug it into a power source, or attempt to power it on. While in said loop the phone will not go past the ATT logo, and as it cycles, at the I9000 screen a robot voice pops up saying restore system. Ive attempted to reflash back to stock with the stock captivate odin3 OCD, but I am having no luck with the phone being recognized by odin (run as admin). I am currently running Mac OSX 10.6 with windows vista on Virtual Box 4.0, and have had luck previously with flashing the phone back to stock after I decided to try new versions of cognition. Currently my phone can only go into download mode and not recovery due to the boot loop. please help asap, this my only means of communication with my family on the other side of the states

Try multiple USB ports/different computers if possible. I had a similar issue after flashing an i9000 rom. I could get into recovery but the power button wouldn't work for selections and in download mode my computer wouldn't recognize it. I just kept at it and eventually it worked.

CB650 Wolf said:
Try multiple USB ports/different computers if possible. I had a similar issue after flashing an i9000 rom. I could get into recovery but the power button wouldn't work for selections and in download mode my computer wouldn't recognize it. I just kept at it and eventually it worked.
Click to expand...
Click to collapse
going to try, redoing my virtual box in hopes that it was something stupid, and also trying the other usb port on my macbook.

Have you tried using a different cable? I had the same issue with a bad flash and Odin would not pick up my phone. If it did, it would nit complete the flash back to stock. I switched cables and it worked fine.
Sent from my SGH-I897 using XDA App

butchatbg said:
Have you tried using a different cable? I had the same issue with a bad flash and Odin would not pick up my phone. If it did, it would nit complete the flash back to stock. I switched cables and it worked fine.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
cable is fine considering I am still able to bring up the gadget serial on my virtual box with the phone.

s0n1cm0nk3y said:
cable is fine considering I am still able to bring up the gadget serial on my virtual box with the phone.
Click to expand...
Click to collapse
Try using ADB..

Edit...misread

rickysa2000 said:
Try using ADB..
Click to expand...
Click to collapse
sadly I wished that work, I tried using adb reboot recovery, and in the attempt, the phone was not able to be detected. Should this be done in hopes to catch it at the right time in the boot loop or in download mode. Ive tried both.

So can you still get into Download mode? If so I would suggest finding another computer to use. For some reason, last week, my PC that I have been using to flash for months decided not to recognize my phone in download mode.
So I switched to my laptop, loaded the ROM. I tried reinstalling drivers and all kinds of stuff but nothing worked. I backed up my PC and re-imaged it and it's working again.

Another person on here had to go and manually remove all references to the USB Driver and re-install it.
I would say just try re-installing (with the phone in DL Mode) the USB drivers with the phone plugged in and see what happens then. Hopefully the OS will detect the phone and you should be golden.
And that mechanical voice is voodoo... need to be careful what folders your deleting even if you are going to flash ODIN.

avgjoegeek said:
Another person on here had to go and manually remove all references to the USB Driver and re-install it.
I would say just try re-installing (with the phone in DL Mode) the USB drivers with the phone plugged in and see what happens then. Hopefully the OS will detect the phone and you should be golden.
And that mechanical voice is voodoo... need to be careful what folders your deleting even if you are going to flash ODIN.
Click to expand...
Click to collapse
Odd I was told your perfectly fine to do so, and then from there do an odin flash. Ive done it before, but oddly enough I think what screwed me was because I did it during while in the rom, vs while in 2.1. I just wanted to try to get a clean slate. doing the master clear code from samsung never really deletes the left overs from say clockwork and such on my internal sd.

problem was the virtual machine, plugged it into a friends computer and all was done within a couple of mins. leave it to emulation falling short :/

Soft Brick (ODIN not helping)

I'd recently flashed the Cognition new build. Yesterday morning I woke up (3 days later) and found that my phone was stuck at the white and blue AT&T screen.
I preformed the Odin 1-click (as I have many times in the past<I'm not a noob to Odin>) I got my phone into a reboot but now it gets stuck at the Galaxy S screen and then goes dark.
Naturally, I used Odin again with different degrees of failure.
1. Gets stuck at file analysis.
2. Gets stuck halfway through and a blue, green or black screen appears.
3. Stuck at the AT&T screen again.
I've used Odin about 25 - 50 times in the last twenty-four hours.
I've also used the other Odin using the I897UCJH2 PDA file that's provided.
The phone booted directly into recovery and gave this error:
E:Can't Mount /dev/block/mmcblk0p1
(I/O error)
E:copy_dbdata_media: Can't mount SDCARD:
copy default media content failed.
And then it went back to the aforementioned black screen of hell.
I have build 1007 in case that's relevant.
I NEED HELP! Preferably a genius.

im having the exact same problem.
please help

I'm not sure if it matters too much, but it could certainly have had something to do with the kernel the newer Cognition would have installed when you upgraded to it.
Are you using I897UCJF6-final-OCD-REV or I897UCJI6-OCD-REV02-Low?
Most people have the first one, I would definitely try the second if it wasn't working.
The last option is to use Odin3 v1.7 (which you seem to have) and using that to update the kernel to a CM7 one and try to install CM7 onto your phone (and then reverting back to 2.1 stock if you wish).
Not sure if any of those options would work, but give me a yell if you need any help with doing any of the above.

You didn't disable the lagfix before you flashed, and your internal partition is still running ext4 but your data partition is back on efs. See this thread.
You will get your phone working, just be patient and go step by step.

Thank You Both
Thank you both but neither of those two options worked.
I was hopeful that the CM would fix it. I played around with that thought yesterday.
I know the difference between ODIN 1-click and ODIN3 v1.70. I've tried both and neither can get me back up and running. I'm hopeful that someone comes to the table with some resolution. This is frustrating.
EDIT:
Oh and I forgot, I've actually used both I897UCJF6-final-OCD-REV and I897UCJI6-OCD-REV02-Low

If you can get into recovery you can get into download mode.
If you tried one-click, what happens when you try to flash back to stock?

I'm able to get into Download Mode AND Recovery.
That's not the problem.
What happens is that when my phone reboots after ODIN 1-click or ODIN v1.70 my phone boots like its supposed to boot and then it gets to the Galaxy S screen and at that point it just craps out and the screen goes black after a few minutes. I think that the problem is that the internal sd card won't mount. When I'm in recovery it says:
"E:Can't mount /dev/block/mmcblk0p1
(I/O Error)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet. please us UI me nu for format and reboot actions"
When I try to format the internal SD using system recovery it says the same thing. I'm able to get my computer to recognize the internal sd card in recovery BUT when I try to access the drive it asks me to format the drive (INTERNAL SDCARD being the drive). It then calls me a sack of SH17 and the computer tells me that it's unable to mount the internal SD.
The problem seems to be that my phone has not mounted any memory what-so-ever. If I were able to perform a masterclear that might help but without it being able to get to the home screen that presents a problem.
It's sh177y because I'll have to end up returning it on warranty AND for that I have to mail it back to Samsung and wait for them to return it to me. I can't go that long without my phone. There are business things that I need this phone for.
Sorry that was just a tiny rant.

You did not read the thread I linked to.
You can't master clear through odin one-click? You should be able to do that without getting to the home screen. Try installing the specific driver package that comes with one click. When the partitions are formatted squirelly, the computer can't recognize the phone as such. Give that a try. You'll get there, be patient.

?
I'm not sure what I missed in that post. I've read and reread that post several times.
To masterclear I believed that you had to be able to get into USB Debugging. I tried to masterclear in both download and recovery mode. Those are the only options where Odin recognizes my phone.

Bwrandon said:
I'm not sure what I missed in that post. I've read and reread that post several times.
To masterclear I believed that you had to be able to get into USB Debugging. I tried to masterclear in both download and recovery mode. Those are the only options where Odin recognizes my phone.
Click to expand...
Click to collapse
I doubt if you have an overclocking kernel from previous rom which you forgot set back to default values when flashing back to stock it's really a pain in the a...

gorgy76 said:
I doubt if you have an overclocking kernel from previous rom which you forgot set back to default values when flashing back to stock it's really a pain in the a...
Click to expand...
Click to collapse
Do you have any suggestions?
Sorry if I seem brash but I've been working on this for three days.

I wish you the best of luck.

ive had similar issues as described in this thread before on ONE pc i have and it can be a real PITA!
Im no real expert but i DO know the pc i use has voltage issues, basically it is running everything fine but things cant seem to charge or external devices tend to act weird occasionally off the usb. What i have done to minimize the similar issues you are describing is
1) plug the usb directly into the back of the pc, basically try different usb ports, some seem to get better voltage/stability.
2) unplug any external devices using usb *printers and whatnot*
3)Alternate PC *sorry this is my end all since i found i have no issues on my laptop*
It doesnt 'sound' like your phone is fubar'd but that your pc isnt getting the strongest connection. again this is comming from someone who had pretty much exactly what your describing and thats what i found
edit: also saw your warranty posting. From me on their 4th captivate and seems to be the final stable one *HORARY!* i can tell you that they will send you a new phone first and you send your defective one back..just do it in the timeframe or they WILL charge your att account

The only thing that I can think of is... Put a kernel that has CWM loaded on to it as recovery (maybe speedmod kernel), boot into recovert (and thus into CWM).
Try deleting all data/cache/etc on it, then try reboot it. Other wise, try and install a ROM straight from CWM (via .zip file, if you can somehow get it on your sdcard).

I'm stuck with phone pc-pc screen. I'v flashed multiple times and went back to stock too without issue. But now... I am stuck at that screen and no button combo works. Ordered a jig but that will take days to get here.. Dont know what to do. And its a work phone. lol Any other things to try?

I'm having a similar issue. I can get into download, and it's recognized by odin. But when I try to write or wipe it just sits at the zimage and does nothing. I've even left it over night to no avail.

Bwrandon said:
Do you have any suggestions?
Sorry if I seem brash but I've been working on this for three days.
Click to expand...
Click to collapse
can your pc still recognizes your phone and copy files towards internal sd card? can you enter 3e recovery? does you lost 3 button combo? file extensions uses lagfix should be one of the culprit and the clock values in the kernel in your previous rom not setting it to default (disabling lagfix and setting voltage and clock speed to default) when flashing back to stock as this would probably causes conflict with the stock 2.1 system. it is realy important not to neglect those default settings as this is the usual reasons for bricked phones that would corrupt the installation process. many people forgot this process due to excitement and ended up with a paper weight phone.

clemmie said:
You didn't disable the lagfix before you flashed, and your internal partition is still running ext4 but your data partition is back on efs. See this thread.
Click to expand...
Click to collapse
gorgy76 said:
file extensions uses lagfix should be one of the culprit and the clock values in the kernel in your previous rom not setting it to default (disabling lagfix and setting voltage and clock speed to default) when flashing back to stock as this would probably causes conflict with the stock 2.1 system.
Click to expand...
Click to collapse
You just can't make it clear enough for some people.
clemmie said:
You can't master clear through odin one-click? You should be able to do that without getting to the home screen. Try installing the specific driver package that comes with one click.
Click to expand...
Click to collapse

Clemmie,
"Try installing the specific driver package that comes with one click."
I'm not sure if you read my OP; I've already done that. I've actually done that several times. I understand how to use ODIN 1.00 and 1.70. I've been using them since they were released.
The lagfix/overclock issue that has been mentioned. I understand that. Fixing it is the problem.

Have you tried my solution? It's definitely worth a try :/

[HELP] SGS stuck at Odin!

Hi all,
I messed up my SGS GT-I9000 yesterday. i was running Darky's Gingerbread & accidentally flashed a theme meant to be for Froyo, and as a result got stuck into a boot loop.
I flashed back the Darky's resurrection to fix the problem but something happened during the Odin process and the phone soft bricked.
Now, I don't get the battery charging sign when connected in power off, there's no response on power button, no response on 3 button recovery combo.
But I am able to get to download mode through 3 button combo. I have tried diff Odins with diff firmwares (stock / resurrection etc) but every time the progress stucks at Factoryfs.rfs (with a teeny bit of blue progress bar on the device).
I have tried different methods on the net but nothing seems to be working since yesterday.
Is there any hope? would really appreciate any help

why are you posting this is the dev section?

Belong to Q&A's. Use 3 file firmware and tick repartition in odin and you are good to go.

junooni said:
Hi all,
I messed up my SGS GT-I9000 yesterday. i was running Darky's Gingerbread & accidentally flashed a theme meant to be for Froyo, and as a result got stuck into a boot loop.
I flashed back the Darky's resurrection to fix the problem but something happened during the Odin process and the phone soft bricked.
Now, I don't get the battery charging sign when connected in power off, there's no response on power button, no response on 3 button recovery combo.
But I am able to get to download mode through 3 button combo. I have tried diff Odins with diff firmwares (stock / resurrection etc) but every time the progress stucks at Factoryfs.rfs (with a teeny bit of blue progress bar on the device).
I have tried different methods on the net but nothing seems to be working since yesterday.
Is there any hope? would really appreciate any help[/QUOTE
I had same problems, try flashing on a Windows XP system
that was the right solution for me! ...I'm on Windows 7 64, this makes randomly problems for me
Regards
Sonic76
Click to expand...
Click to collapse

sonic76 said:
junooni said:
Hi all,
I messed up my SGS GT-I9000 yesterday. i was running Darky's Gingerbread & accidentally flashed a theme meant to be for Froyo, and as a result got stuck into a boot loop.
I flashed back the Darky's resurrection to fix the problem but something happened during the Odin process and the phone soft bricked.
Now, I don't get the battery charging sign when connected in power off, there's no response on power button, no response on 3 button recovery combo.
But I am able to get to download mode through 3 button combo. I have tried diff Odins with diff firmwares (stock / resurrection etc) but every time the progress stucks at Factoryfs.rfs (with a teeny bit of blue progress bar on the device).
I have tried different methods on the net but nothing seems to be working since yesterday.
Is there any hope? would really appreciate any help[/QUOTE
I had same problems, try flashing on a Windows XP system
that was the right solution for me! ...I'm on Windows 7 64, this makes randomly problems for me
Regards
Sonic76
Click to expand...
Click to collapse
i've been flashing roms upto thrice a day on the same system with no problems.
the issue started when i flashed the froyo version of the Valle-mod honeycomb theme onto a gingerbread rom by mistake.
Click to expand...
Click to collapse

You can belive me, flash with n Windows XP machine and your problem gone!
Regards
Sonic76

sonic76 said:
You can belive me, flash with n Windows XP machine and your problem gone!
Regards
Sonic76
Click to expand...
Click to collapse
The OS has no effect on how well ODIN works. Go spread your no fact assumptions somewhere else.

sonic76 said:
You can belive me, flash with n Windows XP machine and your problem gone!
Regards
Sonic76
Click to expand...
Click to collapse
hmmm you're so sure about this that i guess its worth a try. got nothing to lose as it is. now i gotta get my system rebuilt with xp
btw, since the phone doesn't even charge, and i've been trying a million ways to revive it since yesterday, the batt just died and now even Odin is out of the question as the set doesn't charge the battery.
Just made myself a portable desktop charger to charge the battery. lets hope i find a solution soon

Furry Atom said:
The OS has no effect on how well ODIN works. Go spread your no fact assumptions somewhere else.
Click to expand...
Click to collapse
But your 64bit system has an affect, but if you know the problem why ask
for help here?
cheers

Derptard said:
But your 64bit system has an affect, but if you know the problem why ask
for help here?
cheers
Click to expand...
Click to collapse
I'm not the OP. I didn't ask anything.
Oh and BTW having an x64 system still won't affect ODIN. Because x64 versions of windows have an emulation layer that runs x86 apps natively.
If that were the case then every single video game I own except for Crysis wouldn't run properly on my computer.

Furry Atom said:
I'm not the OP, idiot. I didn't ask anything.
Oh and BTW having an x64 system still won't affect ODIN. Because x64 versions of windows have an emulation layer that runs x86 apps natively.
If that were the case then every single video game I own except for Crysis wouldn't run properly on my computer.
Click to expand...
Click to collapse
Sorry, i have read wrong! ;-)
I has had the same problem like junooni, Odin stucks and the phone ends withe an display in different colors, some people says that they have nor problem with Odin 1.3 on 64bit systems, but i had no luck, i flashed many times without a problem with Odin 1.8 and Windows7 64bit but from one day to the other
Odin sucks! ...I take an old WindowsXP machine from a friend and
i have noo problem to reactivate my phone!

Furry Atom said:
I'm not the OP. I didn't ask anything.
Oh and BTW having an x64 system still won't affect ODIN. Because x64 versions of windows have an emulation layer that runs x86 apps natively.
If that were the case then every single video game I own except for Crysis wouldn't run properly on my computer.
Click to expand...
Click to collapse
thanks for your help guys but i guess i've got to keep looking....not willing to give up so easily

Flash jm9.
Sent from my GT-I9000 using XDA Premium App

woolf clubs said:
Flash jm9.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
a link would be appreciated

Try to remove the battery for a few minutes before every flashing using Odin for your case.

junooni said:
a link would be appreciated
Click to expand...
Click to collapse
Everything's on samfirmware.com . Please don't tell me you started flashing custom roms without knowing that.

erm~
Just.. put ur phone in download mode and use odin flash..
flash the official firmware 2.2... then its will not brick..

I think u mess up your kernel and partition what you can try is open kies and connect your phone that's a option on kies for recovery try it else you have to bring your phone to ssc.

Have the firmwares you've tried contained a (modem, CSC, and Code) part?
Also what is ticked in odin?

Ibanez33 said:
Have the firmwares you've tried contained a (modem, CSC, and Code) part?
Also what is ticked in odin?
Click to expand...
Click to collapse
i have the stock firmware from samfirmware.com which is just the PDA file.
I also found a bootloader file in one of the threads that is supposed to have 'phone bootloader update' ticked in Odin.
i've tried in every possible combination but no response. the device doesn't even charge the battery. i can get into download mode but that's about it

[Q] I Killed my Captivate

So lately i have been having a ridiculous amount of issues on my phone. RAM was constantly used up it kicked me out of programs all the time, battery sucked, itd be laggy and jumpy power button stopped working etc. so last night i decided screw it i was sick of it and i was just going to start fresh so first i just did the system reset or whatever on the phone.
Now heres the problem, after the reset i turn the phone on it boots up and goes to the tutorial, when i either skip the tutorial or finish it i get an error message saying the tutorial isnt working properly and asking to force close. so i close it and then all i get is a black screen with the clock on the top. Not of the buttons on it work and it wont do anything but pull down the menu.
ive tried the odin 1 click master clear but it and my computer wont recognize the phone along with me putting it into download mode and trying to flash to stock. Odin doesnt see it and my computer says the drivers are broken and it wont recognize the device.
I re-installed all the drivers but the same results occur. I did however manage to have my computer see it when i put it in samsung keis mode (can still choose that from the drop down menu when i plug it in) however i dont know if that will help anything.
So any and all help will be greatly welcomed as i now am without a phone and need it very soon. Thanks

Delldorado said:
So lately i have been having a ridiculous amount of issues on my phone. RAM was constantly used up it kicked me out of programs all the time, battery sucked, itd be laggy and jumpy power button stopped working etc. so last night i decided screw it i was sick of it and i was just going to start fresh so first i just did the system reset or whatever on the phone.
Now heres the problem, after the reset i turn the phone on it boots up and goes to the tutorial, when i either skip the tutorial or finish it i get an error message saying the tutorial isnt working properly and asking to force close. so i close it and then all i get is a black screen with the clock on the top. Not of the buttons on it work and it wont do anything but pull down the menu.
ive tried the odin 1 click master clear but it and my computer wont recognize the phone along with me putting it into download mode and trying to flash to stock. Odin doesnt see it and my computer says the drivers are broken and it wont recognize the device.
I re-installed all the drivers but the same results occur. I did however manage to have my computer see it when i put it in samsung keis mode (can still choose that from the drop down menu when i plug it in) however i dont know if that will help anything.
So any and all help will be greatly welcomed as i now am without a phone and need it very soon. Thanks
Click to expand...
Click to collapse
If Odin isn't being friendly to your phone, try using Heimdall. You can get all the same things you need from Odin, but it's a different set of drivers and a different program, which might solve your issues.
If you need one, here's a Heimdall One-click to stock Froyo that AdamOutler made. It's really easy to use - just download it, let it install, and click flash.

alright ill try it and see how it goes thanks a lot

no luck. Heimdall doesnt recognize it connected and my computer still says it wont recognize it so im guessing thats the main issue first...

Delldorado said:
no luck. Heimdall doesnt recognize it connected and my computer still says it wont recognize it so im guessing thats the main issue first...
Click to expand...
Click to collapse
If you haven't already, try turning your phone and computer off. Then reboot the computer and let it settle. Once it's all set up, move your USB cable to a port at the back of the computer (or somewhere else on the computer if it's a laptop).
Once you've done that, start up Heimdall. Once it's up and settled, start up your phone in download mode, then hook up the phone.

both have been restarted a couple times but ill try that again. i grabbed a different usb cable as well. this time it allowed heimdall to recognize the device at first but when i started it said no drivers and it i followed the instructions it said after however the options heimdall said werent available. im confused why it would so no drivers as i just reinstalled them and when i plugged the phone in for heimdall it said drivers installed.
but no at the end of trying a couple times the device is back to unrecognized and heimdall cant see it

Delldorado said:
both have been restarted a couple times but ill try that again. i grabbed a different usb cable as well. this time it allowed heimdall to recognize the device at first but when i started it said no drivers and it i followed the instructions it said after however the options heimdall said werent available. im confused why it would so no drivers as i just reinstalled them and when i plugged the phone in for heimdall it said drivers installed.
but no at the end of trying a couple times the device is back to unrecognized and heimdall cant see it
Click to expand...
Click to collapse
Heimdall uses a different set of drivers (libusb) instead of the ones that samsung provides. I would suggest that you go ahead and uninstall the Heimdall drivers as well as the samsung drivers, reboot the computer, and run Heimdall again. Let it finish installing the drivers and be ready, then reboot one more time and try again.

eventually got it working and got it back to stock 2.2 however my 3g isnt working and when i try to run the update on the phone to gingerbread it wont connect to att. i thought maybe i could just flash up to gingerbread but when i put it in download mode and connect it odin still doesnt recognize it and this was after rebooting both

Delldorado said:
eventually got it working and got it back to stock 2.2 however my 3g isnt working and when i try to run the update on the phone to gingerbread it wont connect to att. i thought maybe i could just flash up to gingerbread but when i put it in download mode and connect it odin still doesnt recognize it and this was after rebooting both
Click to expand...
Click to collapse
If you were able to get it to work with Heimdall, and you're wanting to go to stock GB, I would suggest using Adam's UCKH3 Heimdall One-click. This will flash stock AT&T Gingerbread (well.. technically that doesn't exist yet, but..) and the i897 Gingerbread bootloaders at the same time.
Just make sure you have all your important stuff backed up to something that isn't your phone before you do it, and that you have a good connection between your computer and phone.

well that one worked so thanks but still no 3g or any data connection

Delldorado said:
well that one worked so thanks but still no 3g or any data connection
Click to expand...
Click to collapse
Just to check, make sure your IMEI matches the one on your phone.
To do this (assuming you're on AT&T), go to the dialer and type *#06#.
Write down that number, then open your battery case.
Take out the battery, and look on the sticker with the barcode. Above the first barcode should be your phone's IMEI. Double check to make sure those match.
If not, you may have some issues with the contents of your /efs folder.

nvm i figured it out. had to reset the access points or whatever to default. now onto to re rooting. thanks for all the help. know anything about the power button not working? i thought it mighta just been the software before but its still not working. do fixes exist? because i really hate using AnyLock to use my phone.

Delldorado said:
nvm i figured it out. had to reset the access points or whatever to default. now onto to re rooting. thanks for all the help. know anything about the power button not working? i thought it mighta just been the software before but its still not working. do fixes exist? because i really hate using AnyLock to use my phone.
Click to expand...
Click to collapse
It's possible it's dirty and needs cleaning - canned air might be a good solution.

is there a heimdall gb root? cuz as usuall all the odin ones never detect my phone

Delldorado said:
is there a heimdall gb root? cuz as usuall all the odin ones never detect my phone
Click to expand...
Click to collapse
If you're wanting one that's rooted and has CWM, check out the one in my signature. It's stock KH3 gingerbread, with CWM, rooted, but no bootloaders.

hey just wanted to thank you for helpin me out all day. that last heimdall gb helped me about immensely. ive finally been able to install some custom roms and what not successfully. i used to follow every direction super close and nothing ever worked but finally going my way so thanks a bunch ha

[i9000b] BSOD - Phone ! Computer Screen

I had Android 4.0.3 (IceCream Sandwich) on my Galaxy S GT-I9000B (I did install it through Odin, nothing went wrong), but is was laggish (too much for it to handle, I think) and after a few months, I decided to roll it back to 2.3.3 (Gingerbread).
I started the process to install the firmware through Odin3 v1.85 - the file I download (from sammobile.com/firmware, had only one file that I used on the PDA space.
Odin recognized my phone and I started to install it, but after a while my phone was stuck on the downloading screen (2 hours of installation, I tought that something went wrong).
I then turned my phone off to try and install again, but when I turned it on, there were a Phone - exclamation mark - Computer Symbol.
I can get it to dowlonad mode (Volume Down+Home+Power), but when I plug it to the pc, it says "unknown device" and it can't find drivers for it.
I think I have the latest drivers from Samsung (I had from Kies and I re-downloaded a file somewhere from this forum named SAMSUNG_USB_Driver_for_Mobile_Phones_1_5_6_0.exe).
It appears that since windows can't install the drivers, Odin doesn't recognize the device - it was recognizing it before, when I was installing the firmware.
Now I'm stuck - I tried anything I saw in this forum and in other places - I did even pray for a miracle, but it didn't work
I know that there must be a way, but I don't know how.
Before I forget, I'm using Windows 7 Ultimate x64.

If you can get it in download mode everything should be fine, I've had a problem like this, my pc couldn't see the phone in download no matter what. Try to use another USB port, better another PC. Also I've heard that x64 doesn't get along well with Odin. If possible you can try Linux and Heimdall, after all Android is Linux too.

KainFromNod said:
I know that there must be a way, but I don't know how. Before I forget, I'm using Windows 7 Ultimate x64.
Click to expand...
Click to collapse
Ok, k4Z3666, has given you a starting point...the phone is still in download mode but without a booting ROM, so its OK, the problem is your PC, USB cable or USB port. If you want to be quick about it, just try on a lap top..if not a simple Reboot of PC ( after removing power cord) and Phone (after a battery Pull), and a switch to a different USB port at the back of PC can solve this for some...for other solutions try these http://forum.xda-developers.com/showpost.php?p=27205737&postcount=4571 anything else you may need can be found on My Android collections., link below

k4Z3666 said:
If you can get it in download mode everything should be fine, I've had a problem like this, my pc couldn't see the phone in download no matter what. Try to use another USB port, better another PC. Also I've heard that x64 doesn't get along well with Odin. If possible you can try Linux and Heimdall, after all Android is Linux too.
Click to expand...
Click to collapse
I tried other USB Ports and also rebooting. It was working just fine - it seems like a driver problem to me.
My notebook is dead, but I'll try using someone else computer.
Does Odin runs in Windows XP? I might try it in my virtual box - I doubt that it will work, but it is the best thing I have to do untill tomorrow.

I got it working in my mother's notebook - should I try something different? I only have the PDA, should I try a PIT?
I don't know what those do, but I read somewhere that PIT is used to recover bricked phones.
EDIT: I installed only the PDA, it worked fine on the 2nd time (first time, it got stuck but I could make it work changing the usb port and cable).
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?

KainFromNod said:
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
what ROM did you use? Did you do any wipes?
Opps..you got an i900B, so make sure you are only using I9000B ROMS as i9000 is not compatible with your phone
Follow guidelines from here
http://forum.xda-developers.com/showthread.php?t=919219
http://forum.xda-developers.com/showpost.php?p=22941192&postcount=300

KainFromNod said:
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
Assuming that you're on the right rom for your phone can you enter recovery mode? Try reinserting battery, and enter recovery with [vol+, menu button, power on]

KainFromNod said:
I got it working in my mother's notebook - should I try something different? I only have the PDA, should I try a PIT?
I don't know what those do, but I read somewhere that PIT is used to recover bricked phones.
EDIT: I installed only the PDA, it worked fine on the 2nd time (first time, it got stuck but I could make it work changing the usb port and cable).
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
Yep if u want to back to stock u need pit file because ICS use different system file
Why u don't like ICS ? Its way better and faster than sammy ROM even its more stable , I think u should try it again with devil kernel with oc to 1.2 it will fly u can add some live oc which will give more fluidity
Sent from another galaxy powered by CM10 & Syiah

Ok, I'm posting it here just to leave a reply and reference for future generations, as my problem was solved.
xsenman said:
what ROM did you use? Did you do any wipes?
Opps..you got an i900B, so make sure you are only using I9000B ROMS as i9000 is not compatible with your phone
I used a firmware from my country (available here: sammobile.com/firmware/?page=3&model=GT-I9000B&pcode=ZTO&os=1&type=1#firmware) and I wiped the cache (I'm not sure what this means, but I believe it is the 2 options on volume up+menu+power)
Follow guidelines from here
http://forum.xda-developers.com/showthread.php?t=919219
http://forum.xda-developers.com/showpost.php?p=22941192&postcount=300
Click to expand...
Click to collapse
k4Z3666 said:
Assuming that you're on the right rom for your phone can you enter recovery mode? Try reinserting battery, and enter recovery with [vol+, menu button, power on]
Click to expand...
Click to collapse
I was entering recovery mode, but it was giving me some error when I tried to wipe the 2 things that I forgot the name =/
yahyoh said:
Yep if u want to back to stock u need pit file because ICS use different system file
Why u don't like ICS ? Its way better and faster than sammy ROM even its more stable , I think u should try it again with devil kernel with oc to 1.2 it will fly u can add some live oc which will give more fluidity
Sent from another galaxy powered by CM10 & Syiah
Click to expand...
Click to collapse
ICS wasn't faster here - it was laggish and always crashed some common apps (gallery, music player). I believe that the firmware wasn't completely "done" as it was being adapted from another version (my phone is brazilian) and some functionalities that it has (i.e. digital TV) wasn't available.
What I done to correct the boot was simple (I found a tutorial in a brazilian site, so it had all the roms that I needed).
1) Used a PIT and a stock rom to get it back to factory version;
2) Upgraded to Froyo (original) - That was kind of a mistake, the tutorial said to do it because then KIES would update it automatically to Gingerbread. The phone was fully functional, but KIES said that it couldn't update it (it recognized the phone and everything).
The tutorial stoped there, but since I had the ROM, I used Odin to install Gingerbread (the one that was looping) and it was done.
Now I need to remember how to root it because there are some dumb apps who can't get away (i.e. Orkut app, some demo games).
Thank you all for the help!

KainFromNod said:
I was entering recovery mode, but it was giving me some error when I tried to wipe the 2 things that I forgot the name =/
Click to expand...
Click to collapse
From recovery you can always try to flash another kernel, that would probably resolve things too. Anyways the problem's solved, glad to help