1. Making sure that the Edison is receiving enough power from the USB ports (if you can login you should be fine)

2. Making sure you have all of the proper files in the same directory as dtf-util. If I remember correctly, I believe the libusb-1.0.dll file was not included in the Edison firmware download. I downloaded this from another site.

3. Run dtf-util from command line so you can see if there are any errors occurring when it closes. When updating the image it should pick up the Edison fairly quickly, but may need you to unplug and re-plug the two USB cables from your computer in order to become flash-able.

4. After you successfully update the image, do it again using the XDK installer, should be called iotdk_win_installer for windows machines.

Thank you very much for the information and the screenshots. I would like to know if you have the switch pointing to the micro USB ports (you need to have it in that position if you want to use the micro USB port).

Did you try with the Flash Tool Lite Tool? What was the outcome of it?

Yes, I do have te switch towards microUSB ports. I assume the Flash Lite tool is part of the integrated installer, no?

In fact I installed both the integrated installer and standalone driver - trying all the workarounds listed in the various forums. Here is the screenshot of the Integrated installer, the next button is grayed out i.e. it doesn't detect the Edison.

I'm beginning to wonder if there is any issue with the hardware, maybe the microUSB port itself but then I can connect using serial port through Putty. What microUSB port is used for the serial communication?

There could be a problem in the hardware as you said; we could check this by using a power supply. With a power supply the board will not need to be powered through the USB port so we could check if the problem is the board or the power provided from the USB ports on the PCs.

From the picture:

1. This is the port that allows the communication with the Arduino IDE and provides the access to a USB storage partition on the Edison, also allows a RNDIS network interface. When there isn’t a power supply, the Board is being powered by this USB port

2. This is the port used to have access to the Terminal Console on the board

Had this same problem on a Macbook Pro, using the Mini Breakout Board where dfu-util was not finding the Edison, although I had connected both cables properly.

As it turned out, my issue was because I happened to be using a USB cable that I had obtained along with a rechargeable battery, originally used to plug the portable battery into a USB port for charging. After I tested this cable's connectivity, the data leads happened to be not connected, and therefore it was useless as a real standard USB cable should have all 4 contacts connected and able to conduct electricity down the cable.

So, this is just a guess... but have you tried swapping out either of your micro USB cables with ones that you have verified to work with another data using device?

From the output of dfu-util, it appears that your problem is that it's not seeing anything connected:

> flashall.bat
Using U-boot target: edison-blankrndis
Now waiting for dfu device 8087:0a99
Please plug and reboot the board
Dfu device not found Timeout
Did you plug and reboot your board?
If yes, please try a recovery by calling this script with the --recovery option