Thanks for sharing your findings—this is really useful information, especially for anyone working with ESP32-S3 devices.
The distinction between the two drivers (JTAG/Serial and the low-level modem driver) explains a lot of the issues people run into when trying to reflash firmware. It sounds like the main challenge is getting proper access to Bootloader mode when the second driver isn’t installed correctly.
On Windows and Linux, driver installation can sometimes be tricky depending on permissions or conflicting drivers. It might be worth checking if the correct USB CDC/ACM or WinUSB drivers are being assigned, or trying tools like Zadig on Windows to manually bind the device to the right driver.
Also, holding the BOOT button while connecting (or resetting) the device can sometimes force it into Bootloader mode if it’s not entering automatically.
Good call on warning users about Flipper/Marauder firmware—getting locked out of reflashing can be a real headache. Hopefully, with more testing, a consistent driver setup for Windows/Linux can be identified.
Looking forward to any updates you find!