The sequence shown above is of course if you can’t get a working boot loader and partition information onto your s3 prior to flashing your firmware.
Installing ESPEasy will do that for you. After that you only have to replace the firmware (starting at 0x10000) with the WLED firmware via firmware update.
I use the command line esptool for most standard esp32s. Reason is, that for the online flasher the os com port selection window sometimes doesn’t find the correct port or it is not clear which shown com port is which. The esptool elaborates on each com port it finds and states whether there is an esp32 device attached to it or not. So it is simpler to go from there.
I use the online flasher for esp32-c3s because mine often fail to open the default wled-ap after flashing, so then I am stuck there. The online flasher lets you configure the connection to the local wifi network immediately after flashing, and then everything works fine.
The procedure shown above is for my esp32-s3 16M flash memory device. I couldn’t get it to work with either of the two other methods, and the reason seemed to be that the bootloader wasn’t booting properly. So by installing a third party firmware with its own bootloader - which worked fine - I could get around the bootloader problem. Then installing the pure wled firmware over it made everything work without problems so far. I’ll keep dedehais warning in mind, and if there is any problem that might be caused by side effects of that approach I will update this thread accordingly.
I agree I couldn’t get the online one to work properly with it. Used the alternative one where its possible to select your chip but was very hit and miss.