I really don't know what more information to add.
First, I would return the dev board back to factory configuration by setting all jumpers/switches appropriately and then test the Adept programming interface once again.
Also, is the factory builtin self test bit image still available to run? If so, running it should provides some possible answers to likely affected components.
Have you tried programming the FPGA device using the JTAG interface and any storage devices via SPI or other appropriate interface?
If you are, then load and run the factory self test using that method.
You will need to determine the specific cause of the issue, whether or not the issue is with a device failure, PCB flexure issue, etc.
If you can determine the issue is likely to due to a bad solder joint, you maybe able to attempt a reflow of effected solder joints or locate any breaks in traces, if they exist.
Is this possible to fix ? Unfortunately I am not located in the US
It's difficult to say with any certainty. I attempted to purchase several used dev boards of this series, many seem to have PCB flexure damage due to the lack of rubber feet supporting the PCB in critical areas. The cause of the PCB flexure damage, seemed to be due to the previous owner's frequent button and switch closures, with an inordinate amount of force, which flexed the PCB, damaging underlying ball solder joints of nearby BGA packaged components. Of course, as I previously mentioned, your situation maybe entirely different, which is why I would recommend programming via JTAG/SPI every possible component and then test connectivity to the other components using the FPGA or JTAG chain in unit test capacity. As many of the components are accessible via the JTAG chain, it would certainly be a good starting point for diagnosing the specific issue.
It's also certainly possible the damage is isolated to the USB connector or the component implementing the USB interface.
BigDog