yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] WickedNite:
Great tool indeed. Especially for first timers out there, will be alot easier for them now.
[Captivate Android Development] bay_wolf:
I discovered the error in the program. It wasn't asking for administrator rights so it couldn't copy the files it needed to. I'm uploading the fix now. Thanks!

EDIT: Fix uploaded in version 1.2 in the original post.
[Captivate Android Development] FocuseD83:
Wow, bay_wolf, great app! Could of used this a few months ago when I just got my Captivate... Interesting to know that you have been a member of xda since 2007 and only have 29 posts so far, and most in this thread... Great way to get some thanks in your thanksometer... Wouldn't hurt to have a donate link too... ;-)
[Captivate Android Development] Mac11700:
Mod Edit: Quoting a now deleted post.

Mac
[Captivate Android Development] eramming:
lets be gentlemen and keep thing clean here guys.
[Captivate Android Development] bay_wolf:
Thanks! And yeah, I joined xda back in 2007 when I had a windows mobile smartphone. I just lurked back then and forgot about this site until recently when I bought the captivate. And donate link is my signature and the original post. :cool:

I do also know that the download links are down. I'm currently uploading it to a mirror.

EDIT: Also keep all the fighting out of this thread. That's what PMs are for!
[Captivate Android Development] godzulu:
Broken download link...any mirrors?
[Captivate Android Development] Djazin:
Awesome, just in time too was about to flash to stock this morning.
[Captivate Android Development] bay_wolf:
Download links are down but I'm currently uploading version 2.0 which adds a toolbox on the right to install an app, reboot into recovery, and reboot into download. Should be up within an hour.
[Captivate Android Development] HTCOmega:
Dropbox down

Appears that your Dropbox has been overloaded lol Throws up the "too much bandwidth generated" error when I click the link. Anyway we can get a mirror through Multiupload?

--Loving the screenshot, btw. Can't wait to use this when I can get it :p
[Captivate Android Development] bay_wolf:
2.0 Download
[Captivate Android Development] MaverickCoast:
Few observations

After trying out your AIO Captivate Toolbox v2.0, a few observations.......

In Step 3 if you want to run the optional "Master Clear", I had to unplug usb, go to settings>applications>development and select "USB debugging", and plug usb back in before Odin would let me do a Master Clear.

After doing Master Clear, phone was rebooted to USB MTP Application mode.........nothing seemed to happen after pressing Step 4. Repeated prossess above and it rebooted and took me to home screen (Didn't need to press power button).

Pressed Step 5 Got to (blue)recovery TWICE had to choose "reinstall packages" BOTH times to get to green screen (Normal for activating CWM)

Note: First time I got to the install ROM.zip, I got an error message. The second time (after starting all over again) it installed correctly.

I also noticed that at times it seemed like nothing was happening, so maybe some kind of moving display would be helpful to let the user know something IS happening.

In the first two steps, NOTHING was happening and I knew that the debugging setting was probably the culprit, but there was no way to know.

The only major adjustment would be to eliminate the need to recheck debugging. Get that done and it seems like smooth sailing!

Thanks bay_wolf for your contribution.
[Captivate Android Development] PuffinNugz:
You've always needed to put the phone in debug mode before master clearing.. Same as odin. Flashing stock or master clearing turns off debugging.
[Captivate Android Development] sublimaze:
i wish i had this a few months ago. thanks for sharing
[Captivate Android Development] MaverickCoast:
I like to take instructions LITERALLY to see whether they are 1, accurate, and 2, make it easy for someone who only knows what the instructions tell them.....that's all.

Anybody that has "Master Cleared" before knows what you said, BUT, following the instructions in this program word for word you aren't told you need to select debugging. Seems like that should be mentioned, especially for the less experienced! Also, it even says "Do not unplug for any reason". To recheck debugging, you first have to UNPLUG the USB if it is plugged in. A little confusing reading the instructions literally, wouldn't you say? After all, this program is supposed to make it easier!

I was hoping debugging could some how be reactivated through this program without going through the physical steps of doing it. After all, this is a program of convenience! :D
[Captivate Android Development] bay_wolf:
I've refined the instructions to make it easier and hopefully fix your issues. Unfortunately there's no way I can make USB debugging be enabled from the program as I have to have that enabled to send commands to the phone. Also, if you could tell me what error you got that would be great and I'll try to implement a progress bar at somepoint.
[Captivate Android Development] rizzo1001:
I got the same error as DJ, was this resolved. I'm using 2.1 on XP SP3.
[Captivate Android Development] bay_wolf:
Sorry, manual updating isn't going to work. I'll figure a way for updating the program shortly. Until then just download the installer which the 2.2 version will be uploaded shortly. Sorry for the inconvience. Since manual updating won't work I've removed the links in the first post to it.
[Captivate Android Development] Siesta410:
I am getting a "Heimdall.exe - Invalid parameter noinfo noreturn could not be located in the dyanamic link library MSVCR100.dll " error when I try to flash to stock..

It got around three missing DLL errors when I originally tried it, but downloaded them and placed them in /system32/

Help would be appreciated.
[Captivate Android Development] bay_wolf:
Have you installed the C++ redistrabutable that is on the download page?
[Captivate Android Development] Siesta410:
Thanks!

Works perfectly now.

/noob out
[Captivate Android Development] movrshakr:
How do you determine if you need the C++ package other than trying the flash and seeing if it fails?

IOW, What is the name of the program in one's computer to look to see if you have it?
[Captivate Android Development] kevj:
Microsoft VISUAL C++ 2005 Redistributable and/or Microsoft VISUAL C++ 2008 Redistributable will be in your Programs and Features list in Win7. I have both, so I'm not sure which it requires, but the link on bay_wolf's page is for the MS Visual C++ 2010 redistributable. I'd venture to suggest that any of the versions mentioned include the required dll's, but I may be proved wrong...
[Captivate Android Development] Oxicottin:
Bay_Wolf, I cant get the libusb drivers to install I get a time out.... Any thoughts?

Can you put up some links to previous versions?

Thanks,

Chad
[Captivate Android Development] bay_wolf:
Look on the download page a little further down... I have the 2.5 version up there.
[Captivate Android Development] ccdoggy:
I am looking for a little clarification on if the rev 1009 captivate will work with this flash to stock system? Looking through the thread i could not come up with a solid answer just vague possibilities.

I got it refurbished as a replacement and have only flashed one rom onto it so I have not tested any of the flash to stock options.
[Captivate Android Development] bay_wolf:
I just had someone email me and say it worked for them but I don't guarantee anything.
[Captivate Android Development] bigsmitty64:
"Flash custom rom" action is going way to quick and not pushing rom onto the phone. It just auto reboots into recovery and rom isnt there?
[Captivate Android Development] bay_wolf:
Hmmm.. Which version are you using? As I just tested it for both the captivate and rogers version and it worked.
[Captivate Android Development] bigsmitty64:
Using 3.0 Captivate Version
[Captivate Android Development] bay_wolf:
I'll look into it but I think its your computer having the issue. Dumb question but: do you have usb debugging enabled and the phone not mounted?

EDIT: Are you using XP?
[Captivate Android Development] antonyfl:
With 3.0 Rogers Captivate edition, I get the following error : "the application was unable to start correctly (0xc000007b)." I have installed .Net and C++ redist.

edit: this if for flashing to stock
[Captivate Android Development] bigsmitty64:
phone not mounted

usb debugging enabled

windows 7

we are re-downloading 3.0 now just to start from scratch.

Edit: this is being done on another p.c. I'm just relaying the message, We do this on my buds pc, as he has windows. I don't. (holding out for linux version):D
[Captivate Android Development] bay_wolf:
I don't know why this happened. I'd suggest trying version 2.6 instead then. (on the download page)

Okay, if it doesn't work try using version 2.6 as that seems more reliable.
[Captivate Android Development] Fallon:
Nothing terribly ground breaking here, but dam is it convenient to have everything conveniently bundled up like this. So much more convenient than 1 click stock then doing everything manually. Great work & really makes everything much more user friendly.

Might want to make a note in the "Please Select File" dialog for "Flash Custom ROM" that it trys to copy the file over as soon as you hit Ok. I thought things locked up the first time I ran that function. Adding a "this might take a minute to actually copy the file & close the dialog box." message would help.
[Captivate Android Development] bay_wolf:
Thanks, I put it on the download page under the read before downloading section. I'll try to reword it there.
[Captivate Android Development] Loggik:
Bay_wolf: I've loved your AIO tool up until 2.5.

Then I got frustrated and have a problem with how you've changed it in 3.0. You added this Heins... thing. Can't remember the name of it. But whatever it is, it replaced Odin One Click. But this removed the Master Clear feature, which is huge.

Also, the Heins thing requires LibUSB, correct? At least that's what I understand. The LibUSB driver disables Odin from seeing the phone, which is a huge deal to me. I personally think that it was a bad idea to switch from Odin One Click to the Heins thing and then disable Odin from ever working with the LibUSB driver.

I haven't seen anyone else mention this, so I guess it's not that big of a deal that you really need to look into. I'm just saying... I really liked 2.5 over 3.0.
[Captivate Android Development] bay_wolf:
First, If you liked 2.5 over 3.0 then keep that one or download it and reinstall it. This is the reason I left both up...

Second, Heimdall requires LibUSB and yes it disables Odin from seeing the phone. You can unistall the LibUSB driver, just follow the directions in the README file in the Heimdall folder where you installed my program.

Third, as mentioned previously, all Master Clear does is format your internal SD card which you can do from the recovery menu and that's the reason I didn't mind switching to Heimdall.

So, if you like 2.5 that's great. Use it and don't look back. If you want to use 3.0 then use it. Both will continue to have the download links up as some people perfer Hemidall or Odin more. I personally find Heimdall better for my purposes as for me it is harder to brick with and quicker.

Thats all,

Bay_wolf.
[Captivate Android Development] antonyfl:
So there are going to be continuously updated versions of both Heimdall and Odin?
[Captivate Android Development] bay_wolf:
If there are any major bugs with the Odin version they will be patched.
[Captivate Android Development] tkienzle:
That would be AWESOME!!!
[Captivate Android Development] coderunner:
I would also love to see a linux version. I hate having to use a windows machine to odin back to stock.
[Captivate Android Development] kevj:
Having a problem flashing Serendipity 5.12...

be gentle...this is my first custom ROM flash.... ;)

Current setup is:

Stock AT&T Froyo ROM

Rooted (SuperOneClick)

TiB installed and User apps and system data backed up

3e recovery fix applied

CWM installed from AIO Toolbox 3.0

Verified in AIO that debug is enabled prior to flashing....

When I try to install Serendipity, everything appears to proceed OK..the phone reboots into CWM, and I follow the onscreen insructions on the PC to select reinstall packages (only asks once, I assume because I already have the AIO CWM mod installed), then select the ROM.zip.

After confirming I want to install the ROM, I see this:

Installing: SDCARD:ROM.zip
E:Can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)
(Device or resource busy)
e:Can't mount SDCARD:ROM.zip
Installation aborted

I searched to Captivate dev forum for one of the filesystem paths in the error, and found one reference but didn't find any fix (maybe I missed something)

Any help appreciated.
[Captivate Android Development] bay_wolf:
Which version are you using 3.0 or 2.5?
[Captivate Android Development] harpo1:
Bay_wolf I believe he said 3.0 in his post.
[Captivate Android Development] sparker366:
Simplest way is to use the flash to stock option with this tool then flash the rom of choice. I think the 3e recovery is causing you issues. Any time I flash a rom. I always flash back to 2.1 and go from there. Till rom cookers start dealing with the new 2.2 stock rom that came out going back to 2.1 is always safe.
[Captivate Android Development] kevj:
I don't appear to be able to get the Flash to Stock to work in 3.0, so I uninstalled AIO 3.0. and installed 2.5..Still doesn't want to do much....I verify debugging mode, and hit the Flash Stock button, the phone goes into download mode, Odin opens, but never registers the phone. I can get Odin launched (without AIO assistance) and it sees the phone.....
[Captivate Android Development] harpo1:
Make sure you have odin open first before connecting the usb cable.
[Captivate Android Development] sparker366:
Exactly. Odin always needs to be running before you connect the cable.
[Captivate Android Development] kevj:
Thanks for the replies.....

I haven't tried the One-Click Odin full procedure yet (ie entering download mode using adb or button combos)...all I am reporting so far is the AIO launched Odin doesn't see the phone for some reason. The phone DOES go into download mode though...just never shows up in Odin....

UPDATE....

I switched from the USB port on the side of my lappy, which worked flawlessly for the Stock 2.2 upgrade and has been (apparently) connecting OK for bay-wolf's prog, AND was used to SuperOneCLickRoot the phone, to the USB port in the back (shows up in Odin as COM8 instead of COM4) and ODIN went to the Do NOT TURN OFF TARGET warning...

so now I am waiting....

How long to flash stock?....or should I ask, how long to upload the stock image to the phone before it starts to flash...15 minutes now, and no further action....no green progress bar on the phone...should there be? I've seen it when the phone was downloading other attempts at flashing ROMs
[Captivate Android Development] harpo1:
Did you install the drivers from AIO?
[Captivate Android Development] kevj:
Affirmative...at least, when I installed AIO 3.0...I did not re-install after I switched back to 2.5....
[Captivate Android Development] harpo1:
Re-install the drivers from 2.5.
[Captivate Android Development] kevj:
OK...seem to be going back to stock now...I had to kill Odin, and battery pull, which gave me the Phone---!---Computer on reboot. Vol up/down, then plug in put it back in DL mode, and restarted Odin, and the download started (with progress bars)

It just came back up with stock 2.1 firmware.

Thanks all...going to try to flash Serendipity again via AIO...
[Captivate Android Development] harpo1:
Good to hear.
[Captivate Android Development] rsnt:
Hey! Great looking program you have there!

How effective has this been on rogers' captivates?

Anyone used it without any problems?

Any special considerations?

Special instructions?

Cheers

keep up the good work!

P.S: My captivate is running stock JL1 2.2 - fully rooted.
[Captivate Android Development] TRusselo:
umm hold off on the rogers for a bit, or do so carefully,

i just used it the other day for the first time, when flashing stock DO NOT USE PIT FILE!!! DO NOT RE-PARTITION!!! (pit file is for partitioning) the rogers stock does not include dbdata to do re-partition.

i did this and ended up with a recovery error on first boot. had to use ATT one-click to get to boot again, then used AIO captivate toolbox without PIT to return to rogers stock BUT still have ATT first boot screen. (can be fixed).

after that the ROOT from AIO didnt work for me but i used OneClickRoot to root.

i have been in contact with bay_wolf and he's working on the issues.

so it works!!

as long as you dont screw it up!!!
[Captivate Android Development] rsnt:
I thought version 3.0 doesnt use odin? :)
[Captivate Android Development] bay_wolf:
It doesn't. And for anyone who has issues with 3.0 just uninstall and revert to 2.5 as it seems more stable.
[Captivate Android Development] rsnt:
I dont have any issues, I havent even used it yet - I'm just wondering how effective it is? if I need anything particular? any special instructions? maybe a guide here or there? does the rev of the phone matter? etc etc...
[Captivate Android Development] ndmc:
Awesome work... I can't wait to try it out! Thanks alo Icezart!!!
[Captivate Android Development] mortuus.x:
bay_wolf, outstanding job on the toolkit. I downloaded the Rogers 3.0 version over the weekend and having tried a few roms have settled on Firefly 2.3. Pretty happy at this point.

A few questions/suggestions:

1) Restoring the phone to stock with the Rogers v3 doesn't in fact restore it to Rogers stock but rather ATT Stock. Consequently I now have an ATT branded i896 rather than a Rogers branded i896. I thought I had read that this was fixed in v2.5 or 2.6? Perhaps one of the files in the heimdall folders is an ATT vs Rogers one?

2) After restoring to stock, USB debugging is of course disabled. You might want to make mention of this in the Restore to Stock button/process so that fools such as myself don't sit there wondering why they can't immediately click on Restore Custom Rom and have it work :o . Easy to get past, but you've gone so far to making a toolkit that newbies and experts alike can use so this would be one of the final things required for a complete newb to have a total click button solution. Nitpicky I know, just thought I'd mention it

3) In the Restore Custom Rom set of instructions, the process works flawlessly, but perhaps adding in a final step following the Select zip->ROM.zip step that states Navigate within CWM to reboot phone->Enjoy i.e. go back a few steps to the root CWM menu and select Restart Phone Now. Again this is due to the newb in me, but I sat there after applying the ROM.zip a bit unsure as to what I had to do next i.e. apply update.zip? It's only because that's the then active selection in CWM that made me question as to what to do. I guess I had seen so many references to update.zip that I began to question whether or not I had to do something with it. Another nitpicky thing I know, but that first time newb might run into a similar bit of confusion and adding a step to the dialog box would eliminate the possibility of it.

All of those aside, again, outstanding work bay_wolf. Very very cool.

Cheers!
[Captivate Android Development] movrshakr:
If I may, I totally agree with the preceding post about making it totally clear to us stupid newbies what has to be done next at every point.

I totally understand when he says, I sat there not knowing what to do. Please help us. The next thing is obvious to you experts...we however are clueless if this is our first try (as in completely unknowledgeable...see below), and we don't want to brick our phones by saying, well, I guess I should do THIS next.

When I say unknowledgeable, somebody is going to say well, read the forums on how to do it. I have, and I now know 15 different conflicting ways to do it.
[Captivate Android Development] rsnt:
And I agree with both of them - a little guide would be greatly appreciated for us rogers folks... playing around with the program is not a problem, but you cant exactly mess around with this stuff otherwise you might fry it up.

Another thing is, do rev numbers matter at all when using this app?

Keep up the great work!
[Captivate Android Development] bay_wolf:
Sorry for not responding for a bit. I'm currently working on another project dealing with the captivate. Just wanted to say that 2.5 (or 2.6) is a better option for most people.
[Captivate Android Development] rsnt:
Ok? But I've installed 3.0 and the lib drivers... do I uninstall all of it and reinstall 2.6 instead?

and even then, we still need a quick guide, much appreciated! :)
[Captivate Android Development] bay_wolf:
Yes, I would revert to 2.6. For a quick guide:

1- install drivers (if you haven't already) make sure to uninstall the libusb ones if you had installed them (directions in the readme.txt in the heimdall folder where you installed the AIO Toolbox)

2- Press flash to stock

3- Press Flash custom ROM

4- once it's installed press go back in clockworkmod until you get to restart phone and press the power button.
[Captivate Android Development] Chris583:
First I tried 3.0, now 2.5 and I can't seem to get the check for USB Debug to pass.

My Captivate is running a cooked froyo and I'm ready to upgrade to a new rom.

I enabled USB Debug on the phone.

No MOUNT enabled.

Installed Net 4 packages, tried Toolbox 3.0. Installed 64-bit drivers.

It looks like it partially connected, but when I "check for usb debugging mode is enabled," it always says "CURRENTLY DISABLED. To ENABLE go to..... "

Also found a -12 (or-14) error in dos running scripts.

I am running Win 7 Pro - 64 bit. PC was reformatted in the last month or so and I regularly maintain my systems.

I installed with administrator permissions, gave app admin permissions.

I've tried everything I can think of!

THANKS!

EDIT:

Decided to use included Odin 3 click despite the debug warning... and am in the process of reverting to stock through included Odin. This seems to be working and its almost done pushing the stock rom to my captivate.

It recognized device in ODIN right away.
[Captivate Android Development] rsnt:
Ok great - thanks for your reply. I have a question regarding flashing to stock, which firmware is bundled with AIO 2.6 for rogers? Keep one thing in mind, based on some research I've done, rev numbers for each phone may cause problems. I have a rev 1012 for my device, am I gonna have any problems based on that?

THANKS!!!!!
[Captivate Android Development] phrenicthenub:
+1!

I'm about to flash back to stock tonight, but just wanted to make sure this isn't the same as the Odin 1 click that bricks later models (1010 here)..I'm 99% sure it's not because you have to manually load the .pit file from what I've seen, but it seems prudent to check with the experts here!
[Captivate Android Development] backdownup:
Hola. I'm a rogers captivate owner. Not Sure what revision my captivate is (got it in January) but 2.6 works fine to flash. It is indeed the AT&T stock though (Model number listed as I897 in about phone) And the AT&T boot logo is still in place.

Other than that great solution for an AIO Bay Wolf!
[Captivate Android Development] phrenicthenub:
Did you use the proper Rogers link copy of AIO? It seems that that would be the difference between the 2 versions!