I'm trying to update my Godox flash's firmware, but it's not working, and I can't figure out why. I've successfully installed the firmware update application, I've connected my flash to the computer with a USB cable, and loaded the firmware file into the software, but it just won't connect to the device and perform the upgrade.

I think I've got everything set up properly, and I've followed the PDF documentation that was in the update application archive as best I can. What should I check?


Here are some common issues with Godox firmware updating:

Mismatching Firmware File

Whatever you do, DO NOT USE A FIRMWARE FILE FOR A DIFFERENT DEVICE. This is a basic tenet of all firmware updates: firmware is closely tied to hardware configurations, and any hardware differences can mean bricking a device if you overwrite with the wrong firmware image.

While a TT685 and V860II might be identical in UI and features, the fact that they both use different power sources means the firmware images are not identical. Each device has its own separate firmware file for a reason. TT350 users found this one out the hard way when Adorama mistakenly posted the TT350-C update (specifically for adding compatibility with some newer EOS M bodies) as a generic TT350 update. So many non-Canon TT350 owners bricked their flashes with this update, Godox eventually posted the initial versions of the TT350 firmware.

If your device does not yet have a firmware update posted, suck it up and wait until it does.

The only way to fix a mismatch like this is to reload the proper firmware image, but this depends on the device being able to recognize the firmware update request, and sometimes the correct/current firmware image you need is not available. Requesting the firmware from your retailer or Godox may be your only recourse.

G1 or G2

Godox has two separate firmware updating apps. G1 is for pre-AD200 devices, G2 is for AD200 and later devices. Check the Godox downloads page to make sure you're using the correct application for your device. Both applications, when installed, should also install a custom USB driver.

Cable and port

Make sure you're using the correct cable for the device. Newer devices (e.g., A1, Xpro, R2 Pro II, AD400 Pro, X2T) use a USB-C cable, while older devices (e.g., TT685, V860II, AD200) use a micro USB cable. If you are updating an AD200, AD360II, or AD600, make sure that you are using the micro USB port, not the USB-A port that is for attaching an FTR16 receiver if you want to use Godox's older 433 MHz radio system.

If you are using a micro USB cable and the G1/G2 software doesn't recognize the device, consider trying a different cable. Some micro USB cables are solely used for charging and do not do data transfer.

File names

If you downloaded your files from the Godox site, rather than the Flashpoint one, pathnames of either the updates or the applications may contain two-byte Chinese characters which can cause an error. Removing the two-byte characters fixes the issue.

The downloaded file is a .rar archive that contains the firmware update file, and a PDF that contains the revision history for the firmware. If Internet Explorer renamed it as a .man archive and you do not have tools to extract the archive contents, you can simply rename it to .rar.

Also, the .rar format has changed in recent updates so you may simply need to update your archiving application (e.g., update Winzip to the latest version). Or you can use the latest version of the open source 7Zip.

Disable driver signing

Someone on dpreview mentions that you may also need to disable driver signing to get the updater to work.

See also: Flash Havoc's article on the G1 app.

  • 860II & X1T-N have both come through as .fri files rather than .dfu after unrar (checked with multiple rar apps) - should I be worried? [I had to order a new micro USB, so I won't actually worry until Monday] & I solved the 'Windows only' issue by dragging an old PC out of the junk room ;) – Tetsujin May 23 '18 at 16:45
  • 1
    @Tetsujin, no. They use more than one format/suffix, which is why I wrote "typically a .dfu file". I'll edit to remove that bit. I use a BootCamp partition. The other two paths I've heard are virtual machine, or cheap Windows tablet. :) – inkista May 23 '18 at 18:04
  • I have Boot Camp & many Parallels VMs, but I just thought this one needed throwing at a 'real' machine. [I didn't actually drag it out of the junk room, though I've just thrown a Win10 machine in there - I keep a Win7 here for 'necessary evils' ;) – Tetsujin May 23 '18 at 18:31
  • @Tetsujin; yeah, the USB connection requirement is also why I figured just booting into Windows with Boot Camp made more sense than my Parallels VM of my Boot Camp partition. Also, my MacBook is old and slow. But VirtualBox and MS 3-month developer's VMs are free and would work for Linux, too. – inkista May 23 '18 at 18:34
  • OK, that was remarkably simple, once you figure out the instructions; they're a bit opaque. Maybe add, for clarification [this is for V860II-N and X1TN, same procedure] ... Launch app & load .fri file. Switch unit on wait for warmup, switch off, press 'flash' button. Connect USB, switch on [nothing shows, unit stays dark] On app, press Connect. Press Upgrade. Procedure is pretty fast, 10s or so. When complete press Disconnect. Power off unit, disconnect USB. It's ready to go. – Tetsujin May 24 '18 at 12:32

protected by Community Jan 10 at 23:48

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.