yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] AReynante:
I also have a 1007 captivate, I got it today as a replacement phone for my broken cappy, and I am having issues getting off the official 2.2 firmware, to root/cwr/etc.

Edit: I get an error about something missing from my computer, and now odin just doesn't see my phone in the com port.

Win 7 64 bit, and I have the normal drivers installed
[Captivate Android Development] tazman171:
+1! Been saying that forever but....:rolleyes:

Keep up the good work bay_wolf, there are plenty that appreciate it! :cool:
[Captivate Android Development] tazman171:
I have the same problem with Win 7 Pro 64bit, less than a quarter way in a flash to stock with odin windows decided that it didn't like the drivers for download mode and killed them and my phone. No battery charge symbol, nada, zilch, zippo. I did get the phone going again later that night but windows has never recognized my phone in download mode again no matter what drivers I try. Works fine in recovery and normal ops but not in download mode.

I just flash with out odin now and probably done it 30+ times since then with zero issues. Mine's a 1007 build that I got in July with 2.1 eclair so I don't think that part is related, just win 7 as the common culprit. :cool:
[Captivate Android Development] kb9nvh:
OK, just tried this with my captivate version 1012 and was all hooked up, clicked on "flash to stock" and the used odin 1 click option...two windows turned yellow in odin3 oneclick then it uploaded software...topmost left window in odin3 turned green and says PASS, second window below that one turned red and said fail. now my phone flashes the white AT&T window at me continuously. Three button wont do anything.

What did I do wrong? I finally got my Jig and thats why I was trying this tonight.

No one else has mentioned this failure mode in this thread yet???hummmm

Thanks for any help

UPDATE: pulled battery, inserted JIG and yellow digger guy came up (download mode). Used odin 3 button and am following directions again. Looks good so far...ATT screen came up, then something that looked like CWR and now att just shot across and is booting...Whew, that was scary. You should say that if you have a new version phone there's a good chance you will need the jig. Glad I waited to get one before I tried this.

Moving along, I used root to stock and then reinstalled packages...the phone rebooted on its own so I was unable to choose "reboot phone" as directed. Attempted to install my custom ROM which began normally but ended abruptly in a kernal panic. Did a three button reset and got back into the blue menu and reinstalled packages again and then I was able to "reboot phone" from that same menu. So, Looks like I have a pure stock and rooted phone at this point.

Opps, wrong, now all attempts to turn on or do the three button results in Kernal Panic.

Reloaded stock then rebooted, turned on debugging, brought up odin 1click to do a master clear (since there is no "master clear" on odin3v1.81). I was afraid to click on EFS clear or is that the same thing? Which brings up another question is do I have to restore my EFS directory after this clear?

Looks like master clear just seemed to bring up the yellow downloader digging guy and appears to be doing nothing? How long does a master clear take?

OK, last move was a mistake. Not sure how to do a master clear without downloading stock first since thats seems like the only way to bring up the odin with the "master clear" on it (unless EFS clear is the same thing). The phone looked like it was not done downloading the ROM before the blue menu came up asking me to reinstall packages. Not sure if reinstalling packages at this point while the rom download is still happening will cause a problem but that was another little gotcha.

Appears the flash custom rom worked and the rom moved to the phone and got to CWR (green) and installed the ROM.

Clockwork Recovery is now asking me if I want to convert my filesystem since apparently its different than my new rom? I said YES (was I supposed to?)
[Captivate Android Development] bay_wolf:
Yep, that was fine to say yes. It's asking about the lagfix your custom ROM has.
[Captivate Android Development] ippon:
i can't seem to get the drivers right on my win7 32bit laptop either.

the version in the toolbox doesn't install correctly for some reason.
[Captivate Android Development] bay_wolf:
Uninstall any drivers you had previously installed for your phone then download the drivers from the first post (there's a link for just the drivers on there near the bottom). And install those.
[Captivate Android Development] ippon:
that's what i did, like 3 times, actually.

i had some issues with the drivers before, so i figured that i'd start clean and uninstalled everything, then tried to install the drivers on the first post, and sadly no go...

samsung REALLY needs to do a better job with drivers and support.

i really like my captivate, but i don't think my next phone will be samsung.
[Captivate Android Development] tazman171:
Yep, same here been through the uninstall, reinstall, clean registry, re install system drivers, every version of drivers known to work, different usb ports with nothing else hooked up, Win 7 on a new drive with a new install, etc., etc., and still a no go. Every now and the I'll get the phone recognized for a minute or 2 a then windows comes up with a driver did not install properly error and that's that for download mode.

To be honest I haven't tried in a while because it's actually easier to skip odin altogether, you can flash to stock with out odin if you need to. Oh yeah, same problem on my laptop with a new installation of Win 7 Ultimate 32 bit.

Worked for a week and the ....It was no more. That was with the official I-897 drivers and the Galaxy S drivers. At this point I'm leaning toward POS drivers as this is the only issue I've had with Win 7 and on 2 completely different machines. Oh well. :cool:
[Captivate Android Development] spidee601:
Help..I have an ATT Samsung Captivate I897 firmware version 2.2 and Froyo.UCKB1 and I have it in debugging mode. All the samsung drivers

I've tried Rooting the phone with AIO Captivate Toolbox and 1-click root.When it gets to the recovery Utils when I scroll down to re-install packages it always gives me

E-Signature verification failed

Installation aborted.

I can reboot it back to normal but it won't root. Can anyone help me. I know there is probably a thread somewhere but I did look everywhere.
[Captivate Android Development] gautaml:
So I am currently on 2.2 (Rogers official) with SuperOneCLick + RyanOCLF.

Have all the drivers and stuff installed on my Win7 x64 box.

Installed AIO 2.6 and from command prompt can do ADB DEVICES and it sees my device just fine.

So at this point all I do is run the AIO Captivate Toolbox app and click on "Flash to Stock" ?

Do I have to take out my battery or sim card or anything else?

Anyone have a video showing this tool in action? Just being uber careful thats all :/
[Captivate Android Development] spartan062984:
Question: Are you seeing Blue texts or Green texts (CWM)? Unless theres something wrong with the Rootzip, my guess is that it didn't copy the .zip file properly. What do you think Bay-wolf?

SO far everything is good. Only thing, MAKE SURE to have USB debugging enabled, and DO NOT mount (as stated in the OP). I always take my SIM + External SD (if applicable) anytime i Flash period. It's just me being over-cautious tho. Better safe than sorry....wouldn't annything funky happening to my Sim, and or loosing my Data from external SD.
[Captivate Android Development] spidee601:
I am seeing the blue texts
[Captivate Android Development] gautaml:
Another stupid question. When it says "DO NOT MOUNT" it means to "NOT" click the "Connect USB Storage" key.

That is, I should be seeing this in order to proceed, ya?
[Captivate Android Development] spidee601:
My picture is different but USB Storage is on and debuggin is on..I tried the Rogers install also and I get the same thing..I'm sure its got to be something simple but for the life of me I am not seeing it and following instructions to the letter. I hate ATT, why do they have to disable us from being able to install 3rd party apps??
[Captivate Android Development] spidee601:
and I am not mounted
[Captivate Android Development] spidee601:
Nevermind, I finally got the same pic you have. I think the cheap cable that ATT sent with the phone is the problem.
[Captivate Android Development] spidee601:
OK, when I have it in debuggin mode and connect. It shows that I am connect but the little green guy in your picture doesn't pop up nor does it let me choose to and not to click for the USB Storage. When I am not in debugging mode that picture shows up but then of course I cannot run the root program. I've tried it several different ways. Show I download the AIO 3.0 Kit and see if that will push it through?
[Captivate Android Development] bay_wolf:
Rooting 2.2 isn't possible using my program as 2.2 using 3e (i think that's what it is called anyway) recovery. Basically, it won't let the user use reinstall packages to install an unsigned update (which the root file is). There's another root program on here that works for 2.2 but I'm not sure of which it is.
[Captivate Android Development] TRusselo:
there is the recovery fix here http://xdaforums.com/showthread.php?t=909213

now 3e works without signed zips! but to use it without adb you need to be rooted...

hey bay_wolf how about adding that? i know you might still be cheezed at me but i do have good ideas, dont waste them on a grudge!

dont forget the windows quick launch menu stuff we talked about
[Captivate Android Development] spidee601:
Ok, thanks for the help. I was able to sideload a couple programs that I wanted using your AIO 3.0 so I am very very happy about that. Thanks for all the help, I will be donating. Nice program!
[Captivate Android Development] gautaml:
Ok, just did the "Flash to Stock" and it did its thing, booted with i896 Samsung, then Rogers logo which stayed on for quite a while (min or so) and then the screen went off. This is where it sits now (about 5min or so later).

Odin3 ended with a "PASS" in green and this in the message:

Don't see any signs of anything messing up.

Not sure what to do here. Should I hold down Power and power up the device or just wait for it to do its thing?
[Captivate Android Development] gautaml:
Sorry, getting a bit antsy here. A little help please? :(

Phone is still blank screen. I held down Power a few seconds and nothing is happening.

Not sure what to do. :|
[Captivate Android Development] gautaml:
Ok just swiped my hand across the screen and the buttons on the bottom lit up. Weird.

Yet the screen is still blank. Pressing a bunch of buttons (volume, power, etc.) and nothing is going on.
[Captivate Android Development] gautaml:
BTW, I saw no mention of having to remove battery or SIM so I did neither.

Both were left in when I clicked Flash to Stock.
[Captivate Android Development] gautaml:
Ok so now I took out battery + SIM.

Started up Odin3

Plugged in USB

Held down Volume + Power.

Put in battery.

Let go of Power.

Let go of Volume as it went into recovery where I had option to reboot, reinstall packages and a buncha other options.

I chose reboot just to see what happens.

It goes through typical cycle and then ends with Black screen shortly after the Rogers logo (as it has been doing since I started this whole AIO process).

Any suggestion on what to do here to get 2.1 on?
[Captivate Android Development] bay_wolf:
Go back into download mode and press the flash to stock button. It looks like you may have unplugged it too soon. ODIN will reboot your phone for you.

EDIT:

No hard feelings and I'll look into it. Thanks
[Captivate Android Development] gautaml:
I never unplugged at any point.

Ok so I'm still bit unclear on what I should do.

Should I arrive at this step:

Is this where I "Flash to Stock" ?

Can you edit my steps from above and post where I need to do what?

Greatly appreciate it.
[Captivate Android Development] gautaml:
Also when I do flash to stock would I need to pick the PIT and PDA files as well? I assume so?
[Captivate Android Development] gautaml:
Ok just did the 3-button thing using the battery remove process (as per http://www.addictivetips.com/mobile/how-to-unbrick-samsung-captivate/ )

Got to Download screen where it says not to disconnect Target.

In ODIN (which I ran on its own instead of through AIO) and Picked the PIT/PDA files.

Clicked Start. It went through process as before.

After a few min, at this point it is saying "PASS" in the Message section.

I haven't removed USB or touched the phone yet. Will let it sit for however as long to see if anything happens.
[Captivate Android Development] JSS28:
gautaml, the same happened to me and this is how I got it working. Since I could get into Recovery I did a Wipe Data/Factory Reset and a Wipe Cache and then reinstall packages. It was awile ago but I think that was the order and it worked. Tyr it a few times. Before this I also used AIO to just put FireFly on and it worked fine.

[Edit] What version of AIO are you running?
[Captivate Android Development] ippon:
he used 2.6 Rogers.
[Captivate Android Development] gautaml:
Ok, finally got back on stock eclair 2.1 after going into recovery mode and then doing Clear User Data and Clear Cache and then rebooting.

And now Im ready to try this again. :D

Just so I don't screw up, I have a fresh 2.1 to start. Is the process only different in that I remove battery + sim when doing the "Flash to Stock" or do I leave battery in?
[Captivate Android Development] JSS28:
Some people say it does not matter if you leave the SIM in or not. I usually take it out along with my Ext. microSD card but you need your battery in.
[Captivate Android Development] gautaml:
Ok, cool, yea I was thinking the battery was important since the button combo didnt quite work with just USB.

So with all said and done, I guess I should go with the Rogers 3.0 ?
[Captivate Android Development] spartan062984:
When the OP states: "DO not Mount", that means don't click on "Connect USB Storage Key." Correct. The OP specifically says that anytime you use the Program, you need NOT mount. Only have USB debugging on.
[Captivate Android Development] movrshakr:
Things that drive neophytes batty...

so, for all the admonitions to not "mount," there is nothing there on the screen saying anything about

mount

, but we still are not supposed to do it?
[Captivate Android Development] askpcguy:
Basically, the all in one program will only work fully if you enable USB debugging on the phone and plug in the USB cable.

If you see anything on the phone asking to mount the phone to your computer so you can copy files back and forth, there is no need to.

The all in one program needs USB debugging enabled and USB plugged in.

If you mount the phone, the storage on the phone will appear "empty" and that is because it is mounted on the PC so you can copy files. This will cause the all in one program to fail in copying the files required to the device because the device storage is mounted on the PC.

Picture it like this. You flash back to stock eclair 2.1. Odin is done so you pull the USB, enable USB debugging and plug the USB back in. Then you can root using the All in one
[Captivate Android Development] TRusselo:
in earlier android versions i remember it being called mounting! so.. its just a term you noobs aren't too used to seeing! oh SNAP!
[Captivate Android Development] movrshakr:
Well, just what it is that one does when one "mounts" the phone (even though it is not called that except it is called that but the screeen doesn't call it that)--or rather,

exactly

what is it we are supposed to NOT do?

And don't say don't

mount

it !
[Captivate Android Development] JSS28:
I would just stick with 2.6. If it works why switch?
[Captivate Android Development] bay_wolf:
I've made all the download links direct links and will hopefully be uploading them to a dedicated host soon for a mirror (I recently got some web hosting where I can host the files). From now on, all download links will be direct.

EDIT: If you need/want 3.0 just PM me.
[Captivate Android Development] shoman94:
What the heck is going on around here. Money, greed, what happened to people just helping?
[Captivate Android Development] spartan062984:
From the main Man himself. It specifically says in the OP: "Do not mount phone..."

Now before you take it as an insult, know this: Even I consider myself a "noob" but even I know enough to understand.

Simply put: As long as you have USB debugging enabled, don't worry about "mounting" since it is NOT required.

Mounting = allowing YOUR pc to connect/ view what is stored on your INternal/ External SD storage. The only times mounting is required is when you are actually copying/ moving/ cutting files to and from your Internal/ External SD storage.
[Captivate Android Development] TRusselo:
never mind im blind!
[Captivate Android Development] movrshakr:
spartan, Now don't take this as an insult, but I still have not seen what the steps are that one does that would (undesirably) 'mount' the phone. Is it Tools>Map network drive? Everybody says don't mount the phone. I still honestly don't know what (mistakenly) I would do that would cause the mounting to occur--because the word

mount

is not there so I can avoid it!

You come close with "= allowing YOUR pc to connect/ view what is stored on your INternal/ External SD storage." but how? Does computer throw up one of those small dialog boxes that asks if you want to view files--and you just close it? Would you (choose not to do) Tools>Map network drive? What do we not do in terms of clicks and commands!

And I knew baywolf used the term. That was part of what I was saying--the term is widely used (maybe it came out of the unix world?) but this windows person doesn't know what actions 'don't mount' means to not do.
[Captivate Android Development] bay_wolf:
It just means that when you plug your phone into the computer that on the phone's notification panel it will say, "USB connected - Select to copy files to/from your computer." If you press that a screen will come up with a green android guy and have a button labeled "Turn on USB storage". If you press that button your phone will now be "mounted" to the computer. It's just a term that got started being used for it. I know in linux it's called mounting drives so I'm assuming that's where this comes from.

So just leave the USB storage off. Or simpler instructions would be to just plug the phone in and do nothing else on the phone. Haha.
[Captivate Android Development] movrshakr:
Ah, finally. That is exactly what I was looking for. And straight from the king...Thanks!
[Captivate Android Development] gautaml:
In 2.1 when you click "USB Connected" in the pulldown, it will give you option "MOUNT" or "DON'T MOUNT"

Clicking the "Connect USB Storage" in 2.2 is equivalent to "MOUNT" in 2.1

This is what it looks like in 2.2
[Captivate Android Development] Verfassergeist:
Now that I've upgraded to Win7, and I can use this program...are there any roms not supported? I was just under the impression that there was one or two roms that required alittle more hands on approach (I think it was Cyanogenmod?). I was just hoping to use this to attain my epicurean dream for Android.
[Captivate Android Development] spartan062984:
No insult taken my friend. We were all Beginners at some point. :)

I have flashed quite a few Roms (testing + experimental purposes) and modified a few things here and there, but i still feel there is always room for improvement.

I'm not sure is "compatibility" is the question. The Program is simply just a program that basically points CWM + Files (Zips) in the right direction for installation. All i know from the OP is that when you select a Modem Rom (zip file) that it must not contain spaces in between. The AIO is simply just a Learners Best friend. A Genius Program at that.
[Captivate Android Development] movrshakr:
Getting ready to start this--finally, after reading for weeks.

But confusion from the git go:

The OP here, in big type, says

Bay_wolf's AIO Captivate Toolbox 2.6,

but the 2nd post (changelog) shows 3.0 as the latest, and preceding one to be v2.5 (not 2.6).

The "Download Captivate" link says you are getting 2.5

The "Download Rogers" link says you are getting 2.6

I am doing a Captivate, so do I blindly go with the "Download Captivate" link in spite of the inconsistencies? Am I reading too much?
[Captivate Android Development] TRusselo:
the regular captivate version includes AT&T stock

the other includes rogers...

3.0 was removed for now...
[Captivate Android Development] movrshakr:
So the 2.5 for Captivate ATT is right?
[Captivate Android Development] bay_wolf:
Correct. Sorry, I'm cleaning up the OP now. I had to revert the versions because of some bugs.

Cleaning now...

EDIT: Cleaned up a little bit. I'm on vacation right now but will try and get it cleaned up a bit more when I get back home. Basically download the captivate link if you have an AT&T one and the Rogers if you have, well kind of obvious, but a Rogers version.
[Captivate Android Development] movrshakr:
I just downloaded the Captivate AIO, 2.5 msi file, "Install AIO Captivate Toolbox 2.5.msi"

md5 hash computes as 464d5559faa79585fa578bc6162bc5ad

Can anyone confirm that?
[Captivate Android Development] bay_wolf:
Yep, http://xdaforums.com/showpost.php?p=11442360&postcount=227
[Captivate Android Development] movrshakr:
Thanks, baywolf; I appreciate the feedback. I had a stop and restart during the dl and just wanted to be sure it was still OK. Also, it gives a good feeling to know for sure it wasn't injected with something (after being out of your hands on the repository server).

You might want to consider posting on YOUR page the md5's for all of the downloads ...nice safety touch.
[Captivate Android Development] movrshakr:
Is it more complete to say:

Enable USB Debugging (Settings>Applications>Development>USB Debugging)

Plug in phone

Do nothing else on phone
[Captivate Android Development] movrshakr:
Not clear in the on-screen images whether or not phone should be plugged into USB during driver installation. Maybe add?

Also, wow, the driver installation is LONG! ...many minutes. Might want to alert user to that too.
[Captivate Android Development] harpo1:
His program tells you right up top during each step whether it needs to be plugged in or not. If it says nothing you don't have to plug it in. So the drivers can be installed without plugging in.
[Captivate Android Development] movrshakr:
No it does not "...tells you right up top during each step whether it needs to be plugged in or not"; It tells you only when it needs to be plugged in--not when it does NOT need to be plugged in.

Sseeing nothing there gives you NO INFORMATION. You have to ASSUME it means 'don't plug it in' , and when you are doing things that can brick your phone when done wrong, I don't know about you, but I don't like to assume anything!

Why not give positive directions 'don't plug in phone"? Then the user has no question in his mind--has to assume nothing.