yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] AdamOutler:
Beta7 31July2011 Fixed installation of VCC redistributable on each start of program for windows. No changes for Linux or Mac.

no known issues.

Beta6 31July2011 No fixes. Added live PIT View to show what has been flashed and keep an up-to-date log of what's going on in the background.

noted problem with Windows installation of Visual C++ on every run.

Beta5 31July2011 Revised windows installation. No longer installing heimdall.exe to program files. It is now created in temp folder on each start of the application. Visual C++ redistributable is installed when required. Drivers are installed on first click of "flash" button if connection to device is not possible. No changes for Linux or Mac.

Beta 4 30July2011 Fixed installation order for Windows so no reboot/restart is required. Added log into Details window. Each instance gets its own unique and randomized folder. Added logging for flash operations. Fixed unused imports. Fixed links for windows. Reduced memory usage. No changes for Linux or Mac.

Installation of drivers is still a problem on some systems. Use of "Program Files" is not acceptable as a "repository" for binaries, must have an uninstaller or create a binary instance installation.

Beta 3 29July2011 Fixed installer for Windows and Mac. No changes for Linux.

Windows installer is demonstrating problems with order of verifications... VCC redistributable should be installed before heimdall is verified. This leads to having to close the application out and retry. Windows not reporting heimdall installed after installation without reboot. All windows hyperlinks are inoperative.

Beta 2 29July2011: Initial Release.

problem with windows platform installer renders platform unusable. Problem with mac platform does not install newest version of Heimdall.
[Captivate Android Development] Thegodfather156:
why not just flash modems thru CWM?
[Captivate Android Development] DaNaRkI:
Because he choose something "safe" to flash for the screen shot. Cuz some ppl will want to toy with this, but for the very first time will not actually flash unless they see it exactly the screen shot Adam posted.

it is an EXAMPLE

Also, he is showing just what this "one-click" can do.
[Captivate Android Development] xhozt:
Nice job sofar keep it up:)
[Captivate Android Development] 1tontomato:
The hits just keep coming. (;~)

Sent from my SGH-I897
[Captivate Android Development] Thegodfather156:
he seems to be pretty nifty when it comes to Heimdall. i like it, i was just curious what the advantages of this method in comparison to flashing modems thru CWM

you dont have to bold your words, i wasnt trying to be a ****.
[Captivate Android Development] AdamOutler:
As was stated, this is a beta test. I'm not going to release a full package with kernel, factoryFS, Cache and bootloaders for a beta. However, this method makes it much simpler to flash a modem then any other method.

The simplest method for flashing a modem with CWM

1. download package with phone via barcode or transfer to /sdcard/Download

2. Start phone in recovery mode

3. Select install zip from SDCard

4. select Choose zip from sdcard

5. select "download" and then select "modem.zip"

6. scroll down to "yes" and select it

7. select reboot

One-Click:

1. connect phone in download mode

2. download/run this package

3. click flash.

Also, I'll be providing one-click packaging... simply select the Heimdall 1.3 tar.gz file and it will make a one-click out of it. :)

I've got the mac problems worked out. I'm currently working on windows. A beta 3 will be up shortly.
[Captivate Android Development] Thegodfather156:
you are on another level when it comes to developing dude. keep up the good work.
[Captivate Android Development] uberushaximus:
Works fine on Ubuntu 32bit (I already have udev rules configured from a heimdall source build)
[Captivate Android Development] DaNaRkI:
-.-;

@Adam - so.. does this thread mean your hijacking and near constant post in the official Heimdall thread will cool? ;) You were making that thread a lil hard to keep up with. Granted seeing such an interested dev at work was pouring out tons of really neat info :D

@godfather - Just putting it up there as a preventive incase someone else might consider jumping on your question and going off all "I can flash most of that thru CWM, and have never had a problem with ODIN" crap. I've seen some ppl here post things like how Heimdall is bad cuz it was reverse engineered by some guy, and that they would rather stick with such a poorly written program just cuz it came from samsung... Cuz clearly we all love the stock cappy ;)
[Captivate Android Development] kb9nvh:
Tried to run it under windows 7 64Bit. Says I must run as administrator. Although I am logged in as administrator, I atttempted to use the runas command from a command window. Looks like your command line just come back with a syntax error for me. Maybe I did something wrong since I've never used that command before. In any case...problematic to get it installed here.
[Captivate Android Development] AdamOutler:
I'm uploading a new version which corrects that problem now. I didn't realize the changes in 1.3 would ripple the installation across all the platforms.
[Captivate Android Development] AdamOutler:
I've finished uploading commits and a new version of the KC1 beta. Please give feedback on Windows and Mac. Linux has been tested working.
[Captivate Android Development] kb9nvh:
working as connected here!!! After a few installs of drivers and C++ redistributable...then it said I had to install heimdall manually..clicked OK and they I saw the connected message. Looks like no joy on the KC1 upload...I'm perpetually "handshaking with loke" Phone has yellow digger guy on it and it says downloading on the front..??
[Captivate Android Development] Rhiannon224:
Adam, this looks nice, I finally figured out how to install the drivers and find my device. I downloaded the Heimdall suite 1.3.0 and when I click on drivers, it sees the device. Question: if I install the drivers, will it effect the drivers I have intalled for Odin? Also, if I want to use the Heimdall suite for flashing custom ROMs does it work the same as Odin as far as the files and where to put them?
[Captivate Android Development] AdamOutler:
Yes. Heimdall uses the well known and understood Open-Source LibUSB drivers. Odin uses closed source proprietary drivers.
[Captivate Android Development] AdamOutler:
Which version of windows is that?
[Captivate Android Development] kb9nvh:
Win 7, professional, 64bit
[Captivate Android Development] UGART3:
Win7 ultimate x64 issue

Everything seemed to work fine at first, showed device connected then after a few seconds it would disconnect and reconnect over and over and over. I tried to recreate the issue but could not. I tried a few more times and it only disconnected and reconnected once after 30 seconds and it wouldn't do it again. Anyone else see anything like this. I attached a screen shot.
[Captivate Android Development] DaNaRkI:
Log one in as sucessful, both connect and flash. Windows vista 32-bit.

Funny thing, your one click likes to report not seeing heimdall, yet it still connected and flashed. Tested modem did flash properly, as I had data but no voice running an I897 kernel

If it matters my PC as one HD and it is divided into 4 partitions, so heimdall is not on C:\
[Captivate Android Development] AdamOutler:
I'd check your USB cable. To be sure I'll leave mine on overnight then check the log in the morning and I'd like someone else with win7/vista to do the same.
[Captivate Android Development] AdamOutler:
It should not. I'm betting it has something to do with the environmental path not being set. I'll reinstall Win7 on my VM to do some more testing.... I should have set a roll back point. If you reboot it will be found.
[Captivate Android Development] DaNaRkI:
Well actually looks like I didn't even need to reboot. Cuz I just now opened it and it sees heimdall fine. Tho I did already have 1.3.0 installed and it still first came up saying -not installed-, so I let the one click do as it pleased and now it's happy. I even skipped the part of installing a the driver (since it was already set for heimdall) and all went well.

Left phone plugged in over night, had no connection issues what so ever. Not once did it say disconnected, until I unplugged it.
[Captivate Android Development] jmbradd:
Appears to work on Windows 7 professional 64 bit

Heimdall rocks =)
[Captivate Android Development] kb9nvh:
I was able to update my modem to kc1 after the fourth attempt of running the software. first attempt it was stuck at loading loke

second attempt, stuck at setting up the connection (green connection was on however)

third was stuck at loke

fourth, it loaded and rebooted the phone.
[Captivate Android Development] creepyncrawly:
@Adam, I'm going to give you feedback as if I am not computer savvy, but just tell you what I would experience step by step. This isn't strictly accurate since I've done windows development in the past, but never worked with linux or mac os. I am assuming that you wish to test ui as well as the code. I'm running Windows 7 home 64 bit on a Dell Vostro 1720 using IE8.

Clicked on the link from item 2 in the OP. A new tab appeared in IE with a white screen, no text or graphics, and a bar at the top saying "IE blocked this site from downloading files...click here for options...". Click on the bar, click download file, in the resulting file download dialog, click Open. At the end of the file download a small dialog appears saying "Heimdall is not installed. Do you want to install it now?" Click yes. The small dialog goes away.

There is no immediate indication that anything has been installed, ie. no icon on the desktop or the start menu, and searching for the word heimdall produces no results. Searching for the words one click do not find the program. At this point, I wouldn't have a clue what to do.
[Captivate Android Development] AdamOutler:
I left my phone connected to a Windows7 Virtual Machine all night long. No disconnects. It stayed connected the entire time. UGART3, you may want to check your cable connection.

Are you disconnecting and reconnecting your phone a few times? By disconnecting and reconnecting sometimes the loke gets triggered and it can only be used once.

This issue should be fixed in Beta4. It was all on my end.

Beta4 would have been called a Release Candidate (RC1), but I was not able to obtain minimal binaries for Mac platform yet. The Mac installer is still a little larger then 10 megs. I'm trying to get an official Glass Echidna command line only version Heimdall for OS-X which would reduce package size considerably and bring Heimdall One-Click to about 10-11 megs overhead on top of the package.
[Captivate Android Development] creepyncrawly:
Downloaded the beta4 jar. This time I saved the file to disk. Opened the jar file and got the "Heimdall is not installed. Do you want to install it now?" dialog. Click Yes, installation starts, a dialog says it needs to repair or delete the C++ 2010 distributable. Select repair and it works and then says repair is complete with a "finished" button. Dialog goes away and heimdall is not installed.

OK so open the jar file and click NO in the Heimdall is not installed dialog. A web site pops up and the Heimdall One-Click 1.3.0 program window appears underneath all other windows. Select "Install Heimdall v1.3.0" from the help menu and the program installs to the path C:/Program Files (x86)/Heimdall/, containing heimdall.exe and libusb-1.0.dll.

There is no uninstall listing created in the Windows 7 Uninstall or change a program dialog. Not sure what all you are installing, drivers, system files, registry entries, etc. but a Windows program should have an uninstall routine listed in the uninstall programs dialog.

Also doesn't make sense to me, but maybe it's a linux thing. A shortcut from heimdall.exe doesn't open the program. It only opens a dos window breifly with some writing in it, that is not there long enough to read. On the other hand, clicking on the jar file, or a shortcut to the jar file will open the program. Seems to me your installer should create shortcuts on the start menu and/or the desktop.

Tried uninstalling the program by renaming the Program Files (x86)/Heimdall directory, so I could test the installation again, but this time I couldn't get the program to install from the help menu item. Instead, the Heindall One-Click 1.3.0 window became unresponsive.

Edit: Oops. Forgot to mention that once installed, the phone connected immediately.
[Captivate Android Development] AdamOutler:
You're right, it should have an uninstall option on Windows. I'm more of a Linux user. I guess I could deploy the windows heimdall binary to the temp folder and use it there each time... It takes a copy operation, then a unzip operation.. it's a bit of a time consuming process which would add to startup time on each run, but it would conform to Windows standards.

On Linux we have a /bin for Kernel binaries a /usr/bin for "Installed" binaries and a /usr/local/bin for just random binaries. I was trying to use Program Files as a /usr/local/bin which is not appropriate and I will change that somehow to the temp folder. That would also remove an extra UAC popup.

DId you wait for it to finish? I tested repeatedly on my machine. that sounds like the problems from beta 3, not beta 4. Was that Vista or 7?

I need feedback on Mac and Vista... however I will not cross off win7 just yet as I will be doing a revision on the heimdall binary install.
[Captivate Android Development] creepyncrawly:
Windows 7 home 64 bit.

I think I've actually given you some misleading info. After I downloaded and saved the beta4 jar file, I ran the file and selected NO in the "Heimdall is not installed. Do you want to install it now?" dialog. The website page popped up and the program window opened underneath. I then found the help menu item to install the program and ran the installation. It worked fine and the program was installed.

It was after this that I discovered there was not an uninstall feature, so I removed (actually renamed) the Heimdall directory in Program Files (x86) so that I could check the installation sequence again. After this, when I clicked Yes in the "Heimdall is not installed. Do you want to install it now?" dialog, it didn't install correctly. It did the repair to the redisbributable file and then stopped. I tried that a couple times with the same result. Then I tried clicking NO again, and that time the install routine from the help menu caused the window to become unresponsive.

After I forced the unresponsive window to close, I went back and renamed the Heimdall directory to Heimdall, and now the program still works correctly.

I'm guessing that having correctly installed the program first, and trying to uninstall by merely renaming the Heimdall directory was not a complete enough uninstall to test again.

So what steps do I need to take to completely uninstall the program so I can test it again?
[Captivate Android Development] AdamOutler:
Got it... the menu option only installs heimdall. The automatic install does the whole gauntlet.
[Captivate Android Development] 1tontomato:
I'm kinda out for the weekend but I will test this on my mac tomorrow

Sent from my SGH-I897
[Captivate Android Development] AdamOutler:
Good catch there. That lead me to a missing dependency. You were likely not seeing the rotating image at the right, bottom of the screen, nor receiving the status updates on the left bottom... Not critical, but it's definately something I'd want to take care of.
[Captivate Android Development] Add45:
Maybe I'm doing it wrong but I get the same scenario, and when I get past clicking "yes" or "no" on install heimdall and then past the part were it asks me to install drivers for samsung usb composite, it finally says I don't have administrative controls? Tried running all different kinds of commands in CMD but it didn't like the java commands.
[Captivate Android Development] creepyncrawly:
Hope I'm not late to the party on this. I think it's fine to install to Program Files (x86)/Heimdall. It is a windows standard to have an uninstall routine listed in the Uninstall dialog of windows, but if you are just installing a couple files into the Program Files directory, and the device drivers, then an entry in the help file and/or the readme file explaining how to uninstall the program and the device drivers is acceptable. It seems to me that would be a better solution than using a temp file.

Your install routine is not working on my Win 7 setup. I can't even make the menu item repeat the install. I've removed the files and switched back to the original drivers, but regardless, the installation never completes when choosing YES, and the install menu item causes the window to freeze after choosing the NO. I've tried both several times.

One interesting note. I have three "SAMSUNG Android Composite USB Device" drivers showing in device manager. Two are signed and show up under "Universal Serial Bus Controllers". The other one is unsigned and shows up under "Libusb (WinUSB) devices". The last one was installed with zadig.exe from Heimdall 1.3.0, which I just installed this morning. I've switched between the three drivers, and while the Heimdall front end only works with the zadig installed driver, your program will show connected with all three of the drivers.

Edit: After a little additional testing, when one of the non-libusb drivers are active, Heimdall frontend will detect the device but will throw an exception "ERROR: Failed to access device. libusb error: -12" when you try to close PC screen. Your one-click will show the device status as connected, but it chokes when trying to flash the modem. There doesn't appear to be an exception routine for this because it just shows "Detecting device..." and stops.

Consequently, getting a "device status: connected" does not indicate that the libusb drivers have been installed correctly. The tester would have to try to flash the modem to verify that.
[Captivate Android Development] getinlost:
I got connected on Windows 7 Home Premium. It needed to install C++ and I had to manually select the driver.
[Captivate Android Development] apbamaman:
Works with Snow Leopard!
[Captivate Android Development] 1tontomato:
This works however it didn't go smooth the first time. When I clicked on modem-kc1-oneclick.jar it opened just fine. I clicked the detail button and having the two windows open at the same time makes the first window unresponsive. Not knowing what to do I unplugged the phone and plugged it back in and observed the connected disconnected light turn off and on. I then closed the detail window and attempted to flash the modem and got a flash failed response. When I rebooted the phone I got the phone + computer screen no biggie the close pc button fixed it no problem. Apparently once heimdall has established a connection, connecting and disconnecting the phone is a recipe for disaster. I managed to flash successfully three times, and repeat the error twice trying to figuring out what went wrong. Two thing I'd like to suggest 1) make it so you can flash with both windows open. As it is a person can't download a package, view the details and flash without first closing the detail window. Seems silly , but it caused me to second guess, and check the usb connection to the phone 2) add an exception not to flash if the phone has been connected, disconnected and reconnected, because when you do you get a failed flash and a computer +phone screen. Other than that TOTALLY WORKS Mac Snow Lepoard 10.6.8
[Captivate Android Development] AdamOutler:
I've just uploaded beta5. It should resolve all windows problems.

fixed

Uninstall "Samsung Gadget" driver from Devices

Uninstall "Visual C++ redistributable"

fixed

fixed

Awesome

Should be fixed, please test.

http://oneclick.adamoutler.com/files/Modem-KC1-One-Click.jar
[Captivate Android Development] 1tontomato:
Still won't let me flash with both windows open
[Captivate Android Development] AdamOutler:
You mean the detail window? The detail window is a snapshot of what's going on. Its supposed to lock out the window below. It does not provide live updates. I can make it appear over the main window. Is that what you were talking about?
[Captivate Android Development] A.VOID:
Worked flawlessly on Windows 7 64-bit Home Premium
[Captivate Android Development] creepyncrawly:
Beta5 worked all the way through on my Windows 7 64 bit home premium notebook, except that when I got to the driver installation, zadig.exe did not recognise any device. So I checked running the zadig.exe from the Heimdall installation, and still it did not recognise any device. I've been messing with switching the drivers back and forth earlier today, and I also uninstalled the libusb driver and the redistributable before trying the beta5 version, but the original Samsung 64 bit drivers were still installed.

I tried uninstalling and reinstalling the Samsung 64 bit drivers and then tested with the zadig.exe from the Heimdall installation. Connected in download mode and opened Zadig.exe, it appeared to immediately recognise the device, with a listing in the dropdown and a vendor id and a product id, but all three entries went away in less than a second, and subsequently zadig.exe won't recognise any device.

I'm assuming the problem is on my end somehow, and not with your install program, but I won't be able to do any more testing, or use your program, or use Heimdall 1.3.0 on this computer unless I can solve this problem with zadig.exe and get the libusb drivers installed.

Edit: Operator error, lol. I forgot you have to click on the options menu and select list all devices to get the devices to populate the list.
[Captivate Android Development] creepyncrawly:
Tested beta5 on windows xp home. This is a computer that I have never connected the captivate to before. Installed the Samsung 32 bit drivers, then ran the beta5 jar. The install routine loops three times before it completes. First the install redistributables dialog runs and finishes, then the YES/NO dialog appears. Select YES and the repair or uninstall redistributables dialog runs with repair selected, then the YES/NO dialog appears again. The redistributables dialog runs and finishes for a third time, and then the dialog to plug the phone in download mode and click OK. Zadig.exe window appears, installs the drivers and shows success. Then two error dialogs appear, and then the beta5 window appears showing device connected. Tried installing the modem, but it does not do anything. The status window has the following text:

The package has been prepared.

Operating System: Windows Heimdall is not installed.

Installing drivers

Ready.

After being clicked, the flash button is greyed out and the rotating graphic in the lower right is turning faster, but nothing else happens.
[Captivate Android Development] 1tontomato:
Yea that is what I'm talking about. Its an aesthetic thing and not necessary, but it did cause me to second guess myself, which caused an error. Just putting the detail window on top of the one click window would fix it.

Sent from my phone
[Captivate Android Development] creepyncrawly:
Completed the driver installation on my Windows 7 notebook after I realised my error. Driver installed successfully. Tried to install the modem but it wouldn't seem to flash. Pulled the battery and discovered that I had soft bricked the captivate. Don't know why it didn't flash the first try. It progressed to "flashing modem 0%" and stopped. I got it back into download mode and flashed the modem successfully on the next try.

So windows 7 installation seems to be working correctly. I don't particularly like having to go through the whole installation process every time though. And I guess you'll have to give the average user some instructions, ie about the options menu, etc.
[Captivate Android Development] DownNeverOut:
Window 7

Tested and it connects