yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] pantyryder69:
which folder is the correct .inf file located in?
[Captivate Android Development] designgears:
extract the drivers from the OP, browse to them
[Captivate Android Development] kennethpenn:
I've been using this for days now btw. Thanks! Works like a charm every time. Saved my ass over and over and over again
[Captivate Android Development] johnyhoffman:
To all having troubles getting into download mode. I could not for the life of me get this to work. Then I tried the method of letting it go to two black screens while holding volume +/- and power all at the same time, then releasing power. I could NOT get this to work. I was about to give up when I tried that method one last time BUT, I held both the volume up and volume down plus the power button, when the screen went black twice, I released the power button AND I nudged my thumb ever so slightly down so I was only holding the volume DOWN button. Voila! Download Digger! Now I'm factory reset and no longer scared of the Pc!phone screen. Thank you everyone for their previous input and hope this helps some random soul lost in the hell of the Pc!Phone screen purgatory.
[Captivate Android Development] pantyryder69:
It worked! Thanks! You've saved my ass!
[Captivate Android Development] mwiz123:
:) i fixed it
[Captivate Android Development] sepherian:
will the JH2 and JH3 work with 1012 and replace bootloaders?
[Captivate Android Development] DirknJirkn13:
Over the weekend, I tried using Odin3 one click to go back to 2.1 on my new captivate I got from AT&T through warranty. Every time, I got a boot loop with the AT&T splash screen. Then, I tried it on my old cappy and it worked fine. Thankfully, I was able to use odin one click for gingerbread and that worked. Any suggestions?
[Captivate Android Development] Rhiannon224:
This seems to be an issue with some of the newer builds that came with 2.2 installed.
[Captivate Android Development] nasty159:
So I used this on a Samsung Galaxy S i9000 and my phone is n ow bricked. I realise it says captivate only however I need someone to help me fix it.

I know how to flash back to my original rom firmware and kernal, however after using this one click method I can't access my download mode which is (Volume Down + Home + Power) For the i9000. Would using this tool somehow deactivate the download mode from my phone? It worked every single time before flashing this tool, and now I can't get in.

Ideas? PLease help :(
[Captivate Android Development] Johnsondr80:
Try:

Remove battery

Plug in USB

hold volume +&-

Insert battery.

Continue holding untilled you see download mode.

Should only take a few seconds.

If that don't work.

Get a jig.

sign up for dropbox using this link to get 250mb free and help fusion at the same time.

http://db.tt/cCn3zrY

presented by Xdapremium app
[Captivate Android Development] J-Wall:
After i downloaded the drivers for windows 64 i plugged my phone in and clicked the Setup.ex and i keep getting a message that says "The program can't start because dgderapi.dll is missing from your computer. Try reinstalling the program to fix this program." How do i get my driver to work, can someone help?
[Captivate Android Development] g3w3hr:
Something happened to my phone when I was installing clockwork recovery, now it just sits on the ATT screen on boot. I am able to get it into download mode, and I installed the samsung USB drivers. ADB worked previously but now it doesnt see the phone when it is in download mode. So I have odin running, and it sees the phone plugged into com 4 but the background for it is yellow.

Any ideas on how to get the ADB interface to work so I can flash to stock (or another rom) again?

edit: If I click start in Odin oneclick it just says "File analysis..." and sits there.

edit 2: It gets past "File analysis.." then says: "Set PIT file.." followed by "DO NOT TURN OFF TARGET!!" and then just sits there. (com 4 is still yellow)
[Captivate Android Development] Nick James:
I need to take my phone into AT&T for a warranty replacement- this is the software I want to download in order to hide that I ever rooted the phone etc correct?
[Captivate Android Development] mrhaley30705:
Yes. This is it.
[Captivate Android Development] g3w3hr:
So I fixed the problem, here is what I did.

I reinstalled the drivers (samsung x64 from softpedia).

I reinstalled the android SDK.

I updated everything I could in the SDK.

I installed the drivers from SuperOneClick 1.9.5 rooting utility.

I redownloaded Odin oneclick.

I kept trying "Start". I did this about 5 times before it worked.

I'm not sure if this helps anyone else but it worked for me.
[Captivate Android Development] andrewishcool95:
Okay, I feel like this has probably been answered before, but my captivate was shipped with the KB2 firmware and after I flashed cm7 and then back to this, it is in a constant bootloop, and I cant get to recovery or download mode. is there a fix or do I need a jig to get to download?
[Captivate Android Development] simple man:
Try this.http://xdaforums.com/showthread.php?t=963403
[Captivate Android Development] HamToast:
Hey all, I just used this method to return to stock and had a few hiccups along the way. One being the old issue of the phone---!---PC screen. After getting it all straightened out and getting Odin to work, it went to what appears to be a stock system.

However, I've noticed that the menus are NOT stock in appearance, and when I bring up the about phone section it shows a NOT stock kernel, and build number.

I'm a little concerned and frustrated because I needed to do this to send my phone into ATT, and I'm worried they're going to catch on and void my warranty (with my replacement phone already in hand!) Not to mention the button methods of getting to download mode don't work anymore. I have to learn how using adb.

Anyway does anyone think ATT would catch on to this or would I be okay just sending it in like this. I'm frustrated as this was advertised as being able to return my phone to stock...
[Captivate Android Development] dan_maran:
Use the Heimdall package:

http://xdaforums.com/showthread.php?t=1191094&highlight=heimdall

It may be a little tricky, but it worked like a champ!

Remove any USB drives while restoring I found that was my issue.

I wouldn't chance it.
[Captivate Android Development] HamToast:
I guess I'll need to learn how to use Heimdall now too! I need to do some tinkering and see if the method I tried even unrooted, and if I'll need to re-root in order to use the Heimdall package you linked me to.
[Captivate Android Development] dan_maran:
You don't need to be root. Just in download mode I used a jig it was just easier but if you can reboot into download with sgs tools more power to you. The package works great and in fact I'm using it now.
[Captivate Android Development] Pirateghost:
if you used this package, you have a stock kernel and stock build number. if you used a different package, dont know what to tell you.
[Captivate Android Development] qper:
Restored my buddies bricked phone! Thanks:D
[Captivate Android Development] harryk92:
Hello,

I'm not sure what my problem is, but after installing on my laptop, the program does not recognize when the phone is connected in to download mode. When the phone is connected to USB storage it works fine, but won't be recognized in Odin. I feel it might be a driver issue with the 64 bit OS windows 7, but then how does the phone work in mass storage mode? Please help coming from CM7
[Captivate Android Development] studacris:
There are different drivers for mass storage, download mode, and adb. So one could be corrupted but the others work fine...
[Captivate Android Development] gtmaster303:
I swear i love you....

Installed CM 7 on my sister's captivate, and she didn't like the fact that it was kinda buggy. tried reflashing to another rom or backup with no dice. no other rom would flash because i was using CWM 4.0 installed automatically when i installed CM 7. and I already did a full wipe. Kept getting errors, until the phone would finally only bootloop the AT&T world phone logo screen. I thought i was in a deep pile of ****, but you saved me. Can't tell you how relieving it was to boot back into stock. She's now running firefly 3.0. She just wants a stable rom with excellent battery life.

hopefully she likes it. very nit picky, but will never do any modding herself.

By far the most challenging device to mod I've come across

Past devices: Motorola Cliq, MyTouch 3G Slide

Current: HTC G2
[Captivate Android Development] :
If I have Cognition 5 on (latest build), is it safe for me to use this to get back to stock bootloaders? I tried a couple times, but it keeps hanging at "set pit file" and then soft bricking (thank god for 1 click unbrick). Any ideas?
[Captivate Android Development] 4-2ndtwin:
^ U can maybe try the Heimdall i897ucjf6. There's a link in my signature.
[Captivate Android Development] eatonjb:
opps.. edit.. repost.
[Captivate Android Development] mistabeo:
wow, i'm coming from the same boat... CM7 sucks for the captivate. i couldn't flash it to a different rom myself. i don't think that rom was optimized to be used with the captivate, since the battery life was horrible (i was getting 7 hours with 3g turned off and light usage).
[Captivate Android Development] :
Tried a couple more times, and was finally able to get it back. Yay! :)
[Captivate Android Development] gutowscr471:
HELP!!!!!!!

All,

having problems getting back to stock. I was on stock Froyo and wanted CM7, but it just wouldn't take on the phone. I decised to go back to 2.1 using Odin as instructed here.

Basically, ODIN just stops at "DO NOT TURN OFF TARGET". Nothing else happens. If i disconnect i get the BAD screen and have to use my jig to get back to download mode. I can repeat this process time and time again, just can load anything on here. Any thoughts?

Edit: I can't get this phone to take anything. Just gets to download mode, ODIN JF6 recognizes it, but just stops at DO NOT TURN OFF TARGET

EDIT: After 8 times it finally took. Wow that sucked but i'm back and stock 2.1 and will move up from here.
[Captivate Android Development] Aztecbandit:
If u have a not so fast computer it can take a looooonng time
[Captivate Android Development] musavvir:
BRICKED.

Guys, I think i've permanently bricked my phone. I was getting back to stock from my SERENDIPITY VII ROM and things got stuck in the middle (the "DO NOT TURN OFF TARGET" screen). I waited for 15 mins, no progress. I removed the cable, then the battery and now the phone seems to be completely dead. Power button is not working at all.

Would you guys happen to know anything man? I'm pretty devastated here man.

I get no screen man. My phone seems to be completely dead. Do you have any suggestion man? I have heard of the jig but I don't have one (as I live in a remote corner of south asia and it's not easy to get one here.) Will the jig help man? The phone's not responding to anything at all! No power, no screen, no nothing. Would you know anything about this man? Please...:(
[Captivate Android Development] 4-2ndtwin:
If u have no signs of life at all on your phone, then sorry man, I think you are hard bricked. You could get it fixed through Jtag. Search it. You will have to send it off to get it fixed, but it is not expensive. Captivate JTAG
[Captivate Android Development] TayzGpa:
After reading all 202 pages of this thread I have almost given up but thought I would submit one more plea.

Here is the info on my phone. i897

Was running Andromeda 3

1012

Situation: Currently stuck at the phone_!_pc screen due to USB cable falling out during odin flast back to stock rom.

Have tried all the suggested combinations: vol +/_ plus power key

vol + plust power key

vol - plus power key

all of above plus home key

pull battery, and do above.

leave battery in and do above.

odin open, oden closed.

etc, etc, etc.........

Nothing I have tried from this thread seems to get me to the download screen.

Can anyone think of anything I havent tried yet?

Should I try and make a jig?

Dont know what else to try.

thanks in advance.
[Captivate Android Development] 4-2ndtwin:
^ If u have reinstalled drivers, rebooted your computer, and tried multiple usb cords and ports and still not been able to get into download, then yeah, it's time for ya to try a jig. My first jig was homemade and it did the trick. Then I immediately bought a professionally made one.
[Captivate Android Development] kubik1981:
thank you guys so much i owe u
[Captivate Android Development] bird333:
I know this may sound like a strange question, but is this one click safe? I seem to remember reading a while ago that some one-click wasn't totally safe. I think it had something to do with adding the 3-button combo to the phone or something. If someone could also point me to that thread that would be great.
[Captivate Android Development] simple man:
This is the safe method. Although it flashes bootloaders which can be dangerous if you lose power or your usb gets disconnected from the computer, But this version has the primary and secondary bootloaders, which is what you want. The "unsafe " is the one with the three button fix, and it's only unsafe if your flashing to it from gingerbread, because it causes mismatched bootloaders, thus causing a hard brick.
[Captivate Android Development] bird333:
Thanks for the response!
[Captivate Android Development] palvi:
soft brick/hard brick

So my wife was having trouble with her captivate (screen "browning" out, random shut downs, lots of FC's) so I tried to change the ROM to something more stable. It put it into a softbrick, bootloop with the ATT logo.

after some work, I was able to get it into download mode and get it recognized by the computer and Odin 1-click it. It got through START, but instead of rebooting, it went to the grayed out battery charging screen. I wasn't able to do a master clean.

Now, it'll only start into bootloop or the grayed out battery AND in either case, it's not recognized by that computer. Would this be considered a hard brick? And did at least running the START in Odin wipe the root so I can bring it back to ATT?

I've tried so many different combinations of VOL +- power, plug in, you'd think I was playing Mortal Kombat and going for a finishing move. None of them have worked. Adam's unbricker didn't work as the phone isn't recognized by the computer.

Any and all help is appreciated. Thanks in advance!
[Captivate Android Development] studacris:
Make/buy a usb download mode jig. Go to the first post in this thread, st the bottom is 2 links to other stock firmware and the full odin utility tool. Some later builds phones do not accept jf6, the firmware contained in this package.
[Captivate Android Development] Rooster*:
Have you tried this one?

Wake up Odin on your pc.

Plug in your usb cable to the pc only.

Make sure your phone is powered off. (pull / replace battery)

Press and hold volume down then plug in usb cable.

Continue to hold volume down for a few seconds until download mode comes up.
[Captivate Android Development] palvi:
bricked cappy

problem solved.....took it to ATT service center and they gave me a new one. Wow, that was the easiest way to solve that problem. But now she's making me reload everything onto her phone, thrill.:eek:
[Captivate Android Development] shaxs:
I had a Captivate running Fasty 2.5. I picked up the LG Thrill on my renewal and decided to sell a Captivate to a friend. I wanted to restore to stock so like many times before, I decided to use One Click Odin. Unfortunately this time something happened and I get stuck on file analysis. After 20 minutes when I rebooted my phone, I was on the soft brick screen with the computer phone exclamation mark. I tried everything to get into download mode but having model 1008 I could not get into download mode. Bought a jig and got it into download mode.

Connected the phone back and Odin recognizes the phone. Using Master clear it gets stuck on "Master Clear Started....". Pressing start it gets stuck on "File Analysis".

I have tried two different computers, different usb ports, different cables, and running Odin in administrator mode. I cannot get anything to happen. What do I do now?
[Captivate Android Development] Pirateghost:
as stated time and time and time and time again, MASTER CLEAR WILL NOT WORK IN DOWNLOAD MODE

have you tried a heimdall package instead?
[Captivate Android Development] shaxs:
Sorry didnt know that. I do now :)

And no I have not tried a Heimdall package. Where do I get that?

---------- Post added at 03:05 PM ---------- Previous post was at 03:00 PM ----------

Finally got Odin to work.... thanks everyone.

---------- Post added at 03:19 PM ---------- Previous post was at 03:05 PM ----------

Hum, but now I am stuck on the AT&T word phone screen. When I power on I get that screen then I hear the sounds of the next screen (the swwooossshhh and the ding ding, you know I think it was the 3g boot animation) and it stays stuck on the AT&T screen. Hum.....
[Captivate Android Development] Pirateghost:
yep, thats why the warnings throughout the other parts of the captivate forum recommend NOT using the Odin one click on certain build numbers....

hence one of the reasons i recommend Heimdall

try this:

http://xdaforums.com/showthread.php?t=1266172
[Captivate Android Development] shaxs:
Yes that worked thanks. Weird thing is Odin worked many times before.
[Captivate Android Development] EthanMG:
if i use this to flash back to stock and then do a master clear, does it erase my batter stats?
[Captivate Android Development] Pirateghost:
battery stats are held in /data/system

its in the /data partition

when you run this to flash back to stock and use master clear (which is really only doing a format of the sdcard, you can do this yourself), yes you will have successfully wiped your battery stats....and EVERYTHING else on the device...
[Captivate Android Development] dsc522758:
On i9000 bootloaders needing to get to i897

On Mosaic VI and wanting to install MIUI. They say I need to get to I897 bootloaders. Is this what I need? Will it work?
[Captivate Android Development] JKelley103:
No this will put you on froyo/eclair bootloaders.
[Captivate Android Development] dsc522758:
Froyo/Eclair bootloaders mean I897 I think...right?
[Captivate Android Development] studacris:
Yes, eclair bootloaders for the I897.

What build number is your phone? its a 4 digit number on a sticker underneath the battery. Mine for example is 1010 meaning October 2010. If yours is newer than that, and/or it came from the factory with froyo this will probably make your phone boot loop.

Cezar released a package with just the I897 gingerbread boots that you can flash.
[Captivate Android Development] dsc522758:
Build 1006
[Captivate Android Development] studacris:
You're good to go ahead with this then.
[Captivate Android Development] chibixzero:
Yes you can install miui after stock. As long as you have the update.zip recovery just noot into it. And choose reinstall and you will get into cwm Install rom from there. Thats how I doing
[Captivate Android Development] MoRedStar:
I am also coming from MVI wanting to try MIUI, should I use this odin or the one with GB bootloaders. My build is 1010, I want to make sure I am using the correct Odin.

Thanks for any responses.
[Captivate Android Development] studacris:
If you've used this before and your phone didn't bootloop then Either one is fine. Miui is compatible with both sets of boots, just not the I9k's
[Captivate Android Development] MoRedStar:
Thank you, I used it when I came from Phoenix Ultimate to Mosaic VI with no issue, other than that..this would be my second time trying Odin and I am just as nervous about bricking and using it this time as I was the first time.
[Captivate Android Development] argonarcel:
OMGOMGOMG

IT WORKS :D

accidently deleted tw_launcher.apk

so i factory reset... bad idea

but this worked and its back to normal!!!! THANK YOU SO MUCH :D
[Captivate Android Development] abmicyau:
Uhh.. guys. I'm using this to go back to stock from Serendipity VII and right now it's stuck on DO NOT TURN OFF TARGET

WHAT THE HELL AM I SUPPOSED TO DO NOW. T__T

Im too scared to touch anything
[Captivate Android Development] 4-2ndtwin:
Go ahead and unplug the micro usb from ur phone. Pull battery, replace battery and cover. Be sure to have the usb end of the cable plugged into the back of the computer. Close Odin. But this time right click the Odin and run as administrator and then get back into download mode and connect ur phone to the computer and select Start. Don't touch until you see the att screen on your phone as it is starting to reboot. That's when u can unplug the micro usb.
[Captivate Android Development] abmicyau:
sir, i love you. :d
[Captivate Android Development] 4-2ndtwin:
Cool... Hope all turns out good.
[Captivate Android Development] abmicyau:
Yep, I did it again and it worked perfectly. I just flashed MIUI a few hours ago and it's running smoothly. Thanks dude, I was starting to think that my phone had become bricked for good :rolleyes:
[Captivate Android Development] Mastamind89:
Odin finally worked after a few tries
[Captivate Android Development] diakonos:
Has anyone else had trouble getting the JF6 Odin to restore successfully on a "newer" build phone? I recently got a replacement phone, build 1101, and tried the JF6 Odin I've used on my older phone and it appears to flash stock just fine, but when Odin resets the phone at the end of the flash (with the USB cable still attached), all I see is the battery icon restarting over and over. If I disconnect the USB and try to boot the phone, I'm t stuck in the ATT screen boot loop.

I'm downloading the JF6 Odin from the OP here to see if it is any different than the one I've had all along. If that doesn't work, what are my options? Do I need to return to stock for a safe flash of some other ROM? Is there a different "stock" one-click I could use? I'm a big fan of Cognition 4.5.3 and I tried Cog 5v2 but I prefer (for now) 4.5.3 (it has the BLN which I'm having a hard time giving up).

EDIT: I saw the note about JF6 Odin not working on some later phone builds so I'm getting a KB1 (2.2) version instead. I did notice when I got the replacement phone that it had 2.2 already on it. Maybe that should have told me something... :-/
[Captivate Android Development] chibixzero:
That's funny my phone is the same built and I go back to stock fine. Whenever I need it.
[Captivate Android Development] diakonos:
The funny thing is, I got my first replacement back in July just before my 1-year warranty was up to try and get a new phone with a working GPS. I got an 1101 phone at that time too and the stock 2.1 JF6 One-click Odin worked great on that phone. I then proceeded to accidentally step on that phone while running (it fell off my water belt) and my latest replacement is the same 1101 build as the last one but the JF6 2.1 didn't work on it. I'm not sure what the deal is. But, the good news is I got the 2.2 Odin One-click to work great and now I'm running my fave custom ROM again.
[Captivate Android Development] RandomZero:
Just want to add my success story to this thread:

Was trying to flash back to stock Rogers 2.2 from Firefly 3.0 so I could give CM7 a shot but ended up yanking the USB cord.

Whenever I booted it, it would show the Phone to PC Yield icon but I could still get into download mode. Only Odin wouldn't detect the phone. Had to keep rebooting it and switching USB ports before Odin one click would finally detect it and run.

Moral of the story: never give up. As long as you can get into download mode, you're probably good.
[Captivate Android Development] stevrodriguez:
why do the 32 bit drivers say x86?
[Captivate Android Development] mrhaley30705:
Because the 64 bit drivers are x64? No idea, but as long as you know the difference, your good.
[Captivate Android Development] stevrodriguez:
no, when i click on the 32 bit driver link, the download link say SAMSUNG CAPTIVATE DRIVERS x86
[Captivate Android Development] mrhaley30705:
That's the right one.

32 bit = x86

64 bit= x64.
[Captivate Android Development] mrhaley30705:
I thought you were asking for an explanation as to why it was named that way. Sorry.