I need help setting up my TT350S flash to work in Slave mode.
Clarify
which slave mode.
The
SLAVE button on a TT350 is for the "dumb" S1/S2 optical slave modes that don't do anything but let you remotely fire the flash when the sensor under the front red panel "sees" another flash burst. All features like Channel, ID, TTL, HSS, etc. are NOT communicated in that mode. S1 fires the TT350 on the first burst sensed, S2 on the second burst sensed so the "master" can be in TTL and the TT350 won't fire early on the TTL metering pre-burst.
The TT350 also was released before ID settings were added to the Godox radio communication protocol with the release of the XPro transmitter, so it required a firmware update to add that feature to all of the Godox's radio-equipped strobes at the time that could do firmware updates. The TT600 and V850 II can never do ID codes because they can't be firmware updated for it.
Hold down the
MODE button on your TT350S when turning it on, and it will display which version of firmware is actually loaded. The PDF in the TT350S firmware image .rar bundle Godox has on their website states that v1.8 added ID codes. So, if your TT350S is at an early version, you do need to update the firmware on it before you can use them.
It works fine as a flash but when I set up the Slave Mode, I can't access the ID function. It simply doesn't appear anywhere. I just have AF, bL and St when I push the C.Fn button.
That's a very good indication you have an older firmware image loaded. If you purchased used, or you purchased the TT350 a long time ago, it's not uncommon for the firmware to be out of date, given what a PITA Godox firmware updating is.
Well, there's your problem right there.

(Sorry. But my
favorite Chrome plugin at the moment is
"Bye Bye Google AI" ).
Here, try this human-written checklist I wrote. It might not help, but it can't hurt:
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 compute...
photo.stackexchange.com
And at least it will walk you through turning off driver signing.
I did everything possible to try to update the firmware even though the manual clearly states that there is an ID function which I can't find.
Meanwhile, there are folks with transmitters asking "what's this STEP function?" that the user manual wasn't updated to describe after that firmware update went out. Six of one half a dozen of another. Part of the low-low pricetags on Godox gear come from them giving us a firmware update process that only seems straightforward to a firmware engineer (or possibly me, because in my 25+ years as a pro tech writer, I documented hardware, firmware,
and software.)
Godox prictags aren't 1/3-1/5 of OEM flash gear prices for no reason. They don't spend money on UI/UX for firmware updating; they don't do customer support or factory repair or warranty support outside of China. They don't do a ton of integration or corner case testing, and their QA is relatively skimpy and they're probably sourcing components from suppliers who do the same. They don't hire decent translation services. They probably overwork their writers (been there, done that, have seen how the sausages are made).
You're free to complain. But you also wanted an $85 flash. The two things are not unrelated.
I bought the flash in 2019
Huh. The v1.8 update came out in Aug. 2018. If you'd purchased it new, unless it was from some 3rd party seller somewhere, should have been updated.
and never used the Slave mode.
Again, which slave mode?
No matter what I do, both computers that I own don't recognize the connection with the flash and I can't transfer firmware updates. (Both are Windows 11).
You need to turn off driver signing.
I tried several cables that I know transfer data. I'm at a loss what to do.
Some folks have better luck with USB hubs, nobody has luck with USB-C ports on the computer: USB-A has to be used, probably because the G1/G2 software is so old (Windows 7/XP vintage) that its custom driver only
knows USB-A.
Worst comes to worst, find a friend who's a geek and knows their open source command line tools, and use dfu-util instead of G2. The .dfu files for the devices that require the G2 utility to do firmware updates are standard DFU files, and can be loaded that way. BUT. Messing with firmware on this level always carries a higher risk of bricking the device via typo, so you need
someone who's got the chops to do this properly.