Hello,
I recently purchased a CUAV V6X V2 and tried to update to the latest version of PX4 firmware using QgroundControl. The update process was frozen and seemed to have failed, and after unplugging and replugging the USB cable back into PC(running Windows 10 professional), the V6X could no longer be detected by Windows Device Manager(does not show up as a COM device or any other device). The flight controller now seems to be bricked, but the LED lights still turn on when plugged to computer with USB cable. When viewed from the top with the arrow that indicates the front side of the V6X pointing leftwards, the leftmost blue LED flashes periodically when powered on, while the middle yellow LED and rightmost green LED are constant on. Are there any fixes to unbrick the flight controller? An internet search indicates that some flight controllers have a DFU mode that they can be forced into to accept firmware uploads. Does anyone know if the CUAV V6X V2 also has this DFU mode, and if so, how can the V6X be put into this mode? So far, I have tried emailing CUAV’s support mailbox and tried contacting them through their WeChat but have not yet gotten any replies. I have not tried opening up the V6X’s casing, since I managed to brick the flight controller within 5 minutes of unboxing it, and should probably refrain from causing more damage before more info is available.