Hi, when launching ESP Flasher on PopOS i get the following error that results in a core dump.

x@pop-os ~/Downloads % ./ESP-Flasher

(ESP-Flasher:69077): Gtk-WARNING **: 16:37:59.572: /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-ibus.so: undefined symbol: g_memdup2

(ESP-Flasher:69077): Gtk-WARNING **: 16:37:59.572: Loading IM context type 'ibus' failed

(ESP-Flasher:69077): Gtk-WARNING **: 16:37:59.722: /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-ibus.so: undefined symbol: g_memdup2

(ESP-Flasher:69077): Gtk-WARNING **: 16:37:59.722: Loading IM context type 'ibus' failed

(ESP-Flasher:69077): Gtk-WARNING **: 16:37:59.728: /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-ibus.so: undefined symbol: g_memdup2

(ESP-Flasher:69077): Gtk-WARNING **: 16:37:59.729: Loading IM context type 'ibus' failed

(ESP-Flasher:69077): Gtk-WARNING **: 16:37:59.731: /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-ibus.so: undefined symbol: g_memdup2

(ESP-Flasher:69077): Gtk-WARNING **: 16:37:59.731: Loading IM context type 'ibus' failed

(ESP-Flasher:69077): Gtk-WARNING **: 16:37:59.739: /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-ibus.so: undefined symbol: g_memdup2

(ESP-Flasher:69077): Gtk-WARNING **: 16:37:59.739: Loading IM context type 'ibus' failed

(ESP-Flasher:69077): Gtk-WARNING **: 16:38:04.976: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Pop/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)
Bail out! Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Pop/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)
[1]    68415 IOT instruction (core dumped)  ./ESP-Flasher
./ESP-Flasher  4,28s user 1,83s system 49% cpu 12,287 total

I've downloaded and install both release versions of ESP-flasher to my Mac, but nothing happens when I try to run them. I double-click the icon, the program looks like it's opening, and then just ends, with nothing happening. Does anyone have any idea what's happening?

I'm running macOS 10.13.6 on an Intel MacBook Pro.

Hi @Jason2866, I got some issues on production factory that have computers not connected to Internet or with some strange Firewall rules that prevent downloading bootloader

Unexpected error: Error while retrieving firmware file 'https://github.com/espressif/arduino-esp32/raw/2.0.3-RC1/tools/sdk/esp32/bin/bootloader_dio_40m.bin': HTTPSConnectionPool(host='github.com', port=443): Max retries exceeded with url: /espressif/arduino-esp32/raw/2.0.3-RC1/tools/sdk/esp32/bin/bootloader_dio_40m.bin (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1129)')))

Looks like Chineese inspection SSL firewall

Anyway any option to use a local file that I can provide to factory ?

Thanks

I cannot download the ESP_Flasher exe v2,2,3. No matter the browser, it is immediately quarantined by Windows Defender.

My Avira recognized the 64bit Windows installer as a virus and put it in quarantine.

Hi,
I try to flash a "Shelly plus 1PM" with "tasmota32solo1.bin".
"Something" seems start and the 1PM is recognized but then it fails (everytime at the same place):

Using 'COM6' as serial port.
Connecting.....
Detecting chip type... Unsupported detection protocol, switching and trying again...
Connecting....
Detecting chip type... ESP32
Connecting....

Chip Info:
 - Chip Family: ESP32
 - Chip Model: ESP32-U4WDH (revision 3)
 - Number of Cores: 1
 - Max CPU Frequency: 80MHz
 - Has Bluetooth: YES
 - Has Embedded Flash: YES
 - Has Factory-Calibrated ADC: YES
 - MAC Address: 7C:87:CE:64:BA:94
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Chip does not support baud rate 460800, changing to 115200
Connecting......................................
Unexpected error: ESP Chip Auto-Detection failed: Failed to connect to Espressif device: No serial data received.
For troubleshooting steps visit: https://docs.espressif.com/projects/esptool/en/latest/troubleshooting.html

Any idea what I'm doing wrong here?

BR,
FFNB

Firefox Version 126.0.1
Windows 10

Error encountered;

https://github.com/nalexandru/api-ms-win-core-path-HACK/releases/tag/0.3.1

Place a copy of the file api-ms-win-core-path-l1-1-0.dll (x86) in /windows/system32. I have verified that ESP-Flasher2-Windows-x86.exe does now run correctly without error messages.

The Programm can not be startet because api-ms-win-core-path-l1-1-0,dll is missing.

Same with 32bit Version under Windows 7 Pro

I already deleted the files but when I just downloaded the latest ESP-Flasher.exe it wouldn't allow the download with Chrome and when I tried with Firefox it let me know there was a virus in the program.

I'm came from WLED firmware project. We using different partitions for our firmware. I would like to ask if it possible to use with your ESP flasher different partitions? If so how I can do it? I would like to inform you that I'm not a professional developer but I'm helping for WLED project to build bin files and wish to help with proper ESP flashing tool. Please help us.

The esp32 keeps rebooting after flashing this binary (v13.2.0):
https://ota.tasmota.com/tasmota32/release/tasmota32.bin

But it worked with v12.5.0 binary:
https://ota.tasmota.com/tasmota32/release-12.5.0/tasmota32.bin

ESP Flasher is very good, any chance to keep it working with tasmota v13?

Hello, unfortunately the Appimage won't start on Ubuntu 22.10. The terminal output is

(ESP-Flasher:23177): GLib-GIO-ERROR **: 16:20:19.396: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'
Trace/Breakpoint ausgelöst (Speicherabzug geschrieben)

Can this be fixed? From what i googled, this has something to do with Wayland.

Can you add the Read feature to back up the firmware?

https://www.virustotal.com/gui/file/5401efd257572d78a62c719a95ebae69d0eb9ad4eacceb58c8ee8c014fa577db

Shame on you!

Hi,

When I select "browse" the app crash

./ESP-Flasher
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_set_static_name
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so

(ESP-Flasher:44296): Gtk-WARNING **: 19:24:09.212: /lib/x86_64-linux-gnu/libibus-1.0.so.5: undefined symbol: g_task_set_static_name

(ESP-Flasher:44296): Gtk-WARNING **: 19:24:09.212: Loading IM context type 'ibus' failed

(ESP-Flasher:44296): Gtk-WARNING **: 19:24:09.244: /lib/x86_64-linux-gnu/libibus-1.0.so.5: undefined symbol: g_task_set_static_name

(ESP-Flasher:44296): Gtk-WARNING **: 19:24:09.244: Loading IM context type 'ibus' failed

(ESP-Flasher:44296): Gtk-WARNING **: 19:24:09.244: /lib/x86_64-linux-gnu/libibus-1.0.so.5: undefined symbol: g_task_set_static_name

(ESP-Flasher:44296): Gtk-WARNING **: 19:24:09.244: Loading IM context type 'ibus' failed

(ESP-Flasher:44296): Gtk-WARNING **: 19:24:09.245: /lib/x86_64-linux-gnu/libibus-1.0.so.5: undefined symbol: g_task_set_static_name

(ESP-Flasher:44296): Gtk-WARNING **: 19:24:09.245: Loading IM context type 'ibus' failed

(ESP-Flasher:44296): Gtk-WARNING **: 19:24:09.245: /lib/x86_64-linux-gnu/libibus-1.0.so.5: undefined symbol: g_task_set_static_name

(ESP-Flasher:44296): Gtk-WARNING **: 19:24:09.245: Loading IM context type 'ibus' failed

(ESP-Flasher:44296): Gtk-WARNING **: 19:24:09.255: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_set_static_name
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_set_static_name
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_set_static_name
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
**
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/breeze-dark/status/16/image-missing.svg: Unable to load image-loading module: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: /tmp/_MEIXsohUw/libstdc++.so.6: version GLIBCXX_3.4.30' not found (required by /lib/x86_64-linux-gnu/libicuuc.so.72) (gdk-pixbuf-error-quark, 5) Bail out! Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/breeze-dark/status/16/image-missing.svg: Unable to load image-loading module: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: /tmp/_MEIXsohUw/libstdc++.so.6: version GLIBCXX_3.4.30' not found (required by /lib/x86_64-linux-gnu/libicuuc.so.72) (gdk-pixbuf-error-quark, 5)
Abortado (`core' generado)

Hi,

just downloaded ESP-Flasher-Windows-x86.exe to flash my ESP cam but i cant as MS Security Essentials blocks and removes because it finds some Trojan:Win32/Zpevdo.B in the file

https://www.microsoft.com/en-us/wdsi/threats/malware-encyclopedia-description?name=Trojan%3aWin32%2fZpevdo.B&threatid=2147729093&enterprise=0

Using 'COM3' as serial port.
Connecting....
Detecting chip type... Unsupported detection protocol, switching and trying again...
Connecting...
Detecting chip type... ESP32
Connecting...

Chip Info:

• Chip Family: ESP32
• Chip Model: ESP32-D0WDQ5-V3 (revision v3.1)
• Number of Cores: 2
• Max CPU Frequency: 240MHz
• Has Bluetooth: YES
• Has Embedded Flash: NO
• Has Factory-Calibrated ADC: YES
• MAC Address: 24:DC:C3:C2:9D:58
  Uploading stub...
  Running stub...
  Stub running...
  Changing baud rate to 1500000
  Changed.
• Flash Size: 4MB
  Unexpected error: Error while retrieving firmware file 'https://raw.githubusercontent.com/Jason2866/ESP_Flasher/factory/bootloader/esp32/bin/bootloader_dout_40m.elf': 404 Client Error: Not Found for url: https://raw.githubusercontent.com/Jason2866/ESP_Flasher/factory/bootloader/esp32/bin/bootloader_dout_40m.elf

(German)

Seems to be serious?https://www.virustotal.com/gui/file/c0cdec2fc219d78d915e929c7d38f5942dbb43ae020078a28064ba839459e6e8

Older version of .exe
https://www.virustotal.com/gui/file/ba140cd0ba1b70af907ed15247de60aa1ec6989ebc2c01d843983c0f9ba7140a

Hi!

I try to use ESP_Flasher but I get an error while installing via pip:

pip install esp-flasher
Defaulting to user installation because normal site-packages is not writeable
Collecting esp-flasher
  Using cached esp_flasher-1.4.1-py3-none-any.whl (111 kB)
Requirement already satisfied: requests<3,>=2.24.0 in /home/jeroen/.local/lib/python3.8/site-packages (from esp-flasher) (2.27.1)
Collecting wxpython<5.0,>=4.0
  Using cached wxPython-4.2.0.tar.gz (71.0 MB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error
  
  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [8 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-zyftjlzj/wxpython_11e66a7a8d8f422ab83c39fad694ad67/setup.py", line 27, in <module>
          from buildtools.config import Config, msg, opj, runcmd, canGetSOName, getSOName
        File "/tmp/pip-install-zyftjlzj/wxpython_11e66a7a8d8f422ab83c39fad694ad67/buildtools/config.py", line 30, in <module>
          from attrdict import AttrDict
      ModuleNotFoundError: No module named 'attrdict'
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

in spi_flasher/common.py
The function read_firmware_info provides up to 4 flash_mode (qio, qout, dio, dout), but only qio and dio bootloaders are provided in esp32/bin (eg bootloader_dio_40m.elf)
I do not know the difference beetwen each flash mode, but using only dio mode seem to run well, so i replace the line 167 of common.py by
flash_mode = {0: "qio", 1: "qio", 2: "dio", 3: "dio"}.get(flash_mode_raw)

allowing the tasmota upload to complete successfully

Hi there. Just downloaded and used v1.1 (I think, there's no clear version indication on the software anywhere I can find) on a factory-new ESP32-Cam module with a freshly downloaded tasmota32-webcam.bin firmware.

It seemed to do the usual work, but after finishing the Console window was scrolling VOLUMES of random characters occasionally tagged with a timestamp and sometimes a few other lines I couldn't read. I couldn't stop the scrolling lines; they were CONSTANTLY churning past.

The only way I could find to interrupt it was to unplug the device, which caused the application to instantly crash and disappear.

I tried again a second time, but this time it was vomiting text I couldn't read (or log, or stop, or slow down) over and over and over and over and over .....so I unplugged the device again, and tried a third time.

Same results.

After that, I manually downloaded all of the files from the Tasmota Github and manually flashed it using the following command;
esptool.py --chip esp32 --port COM9 --baud 921600 --before default_reset --after hard_reset write_flash -z --flash_mode dout --flash_freq 40m --flash_size detect 0x1000 bootloader_dout_40m.bin 0x8000 partitions.bin 0xe000 boot_app0.bin 0x10000 tasmota32-webcam.bin

Manually flashing worked fine. Reflashing with ESP_Flasher AFTER manually flashing results in the exact same behavior -- repeated, scrolling, spamming text that goes past so fast I can't read it.

I'd love to give more information, but the application doesn't leave logs behind to examine.

When downloading...

• ESP-Flasher-Windows-x86.exe
• ESP-Flasher-Windows-x64.exe

... from https://github.com/Jason2866/ESP_Flasher/releases, they are immidiately blocked by Microsoft. According to Microsoft Defender Antivirus, Win32/Wacapew.C!ml is found. Recommendations given is to remove this file.

File: v.1.4.1

This might have nothing to do with the flasher as I am trying to flash a couple of these devices for the first time. I have flashed dozens of other Sonoff models without issue.

The flash appears to complete but the device never boots.

This was using tasmota32s3.bin

I have tried all the different ESP32 firmware versions and get similar results.

If anyone has any ideas I'd love some help.

Logs below:

Using '/dev/ttyUSB0' as serial port.


Detecting chip type... Unsupported detection protocol, switching and trying again...
Connecting...
Detecting chip type... ESP32
Connecting...

Chip Info:
 - Chip Family: ESP32
 - Chip Model: ESP32-D0WDQ5-V3 (revision 3)
 - Number of Cores: 2
 - Max CPU Frequency: 240MHz
 - Has Bluetooth: YES
 - Has Embedded Flash: NO
 - Has Factory-Calibrated ADC: YES
 - MAC Address: C0:49:EF:D1:C7:38
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
 - Flash Size: 4MB
 - Flash Mode: qio
 - Flash Frequency: 80MHz
Erasing flash (this may take a while)...
Chip erase completed successfully in 13.0s
Flash will be erased from 0x00001000 to 0x00005fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x0000e000 to 0x0000ffff...
Flash will be erased from 0x00010000 to 0x0016cfff...
Flash params set to 0x002f
Compressed 18560 bytes to 12759...
Writing at 0x00001000... (100 %)
Wrote 18560 bytes (12759 compressed) at 0x00001000 in 0.5 seconds (effective 298.6 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 129...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (129 compressed) at 0x00008000 in 0.0 seconds (effective 613.7 kbit/s)...
Hash of data verified.
Compressed 8192 bytes to 47...
Writing at 0x0000e000... (100 %)
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 837.8 kbit/s)...
Hash of data verified.
Compressed 1428912 bytes to 1008146...
Writing at 0x00010000... (1 %)
Writing at 0x0001690d... (3 %)
Writing at 0x0001ce8d... (4 %)
Writing at 0x0002750b... (6 %)
Writing at 0x00031089... (8 %)
Writing at 0x000399b6... (9 %)
Writing at 0x000418f4... (11 %)
Writing at 0x00049d81... (12 %)
Writing at 0x00055c14... (14 %)
Writing at 0x0005b4b0... (16 %)
Writing at 0x00061098... (17 %)
Writing at 0x000663a8... (19 %)
Writing at 0x0006b433... (20 %)
Writing at 0x00070709... (22 %)
Writing at 0x00075c28... (24 %)
Writing at 0x0007ad16... (25 %)
Writing at 0x00080272... (27 %)
Writing at 0x00085b38... (29 %)
Writing at 0x0008ad73... (30 %)
Writing at 0x0009080f... (32 %)
Writing at 0x00096391... (33 %)
Writing at 0x0009b954... (35 %)
Writing at 0x000a085b... (37 %)
Writing at 0x000a5794... (38 %)
Writing at 0x000aa990... (40 %)
Writing at 0x000afaa5... (41 %)
Writing at 0x000b5080... (43 %)
Writing at 0x000ba327... (45 %)
Writing at 0x000befb1... (46 %)
Writing at 0x000c3dc6... (48 %)
Writing at 0x000c8f29... (50 %)
Writing at 0x000cdce8... (51 %)
Writing at 0x000d2fec... (53 %)
Writing at 0x000d7eae... (54 %)
Writing at 0x000dcc70... (56 %)
Writing at 0x000e1c9b... (58 %)
Writing at 0x000e6b7f... (59 %)
Writing at 0x000ebc7d... (61 %)
Writing at 0x000f177b... (62 %)
Writing at 0x000f6b26... (64 %)
Writing at 0x000fc3da... (66 %)
Writing at 0x001015ad... (67 %)
Writing at 0x0010641a... (69 %)
Writing at 0x0010b556... (70 %)
Writing at 0x00110515... (72 %)
Writing at 0x001155ec... (74 %)
Writing at 0x0011a411... (75 %)
Writing at 0x0011f45b... (77 %)
Writing at 0x001244fc... (79 %)
Writing at 0x00129f71... (80 %)
Writing at 0x0012f596... (82 %)
Writing at 0x001343c6... (83 %)
Writing at 0x00139527... (85 %)
Writing at 0x0013e53d... (87 %)
Writing at 0x00143856... (88 %)
Writing at 0x00148d24... (90 %)
Writing at 0x0014e9d6... (91 %)
Writing at 0x0015407a... (93 %)
Writing at 0x0015944d... (95 %)
Writing at 0x0015e672... (96 %)
Writing at 0x00163d51... (98 %)
Writing at 0x0016995d... (100 %)
Wrote 1428912 bytes (1008146 compressed) at 0x00010000 in 23.5 seconds (effective 486.5 kbit/s)...
Hash of data verified.

Leaving...
Hard Resetting...
Hard resetting via RTS pin...
Done! Flashing is complete!

Hi Jason, thanks for this flasher tool, it works beautifully.

I use many Atom Lite devices, which support these serial speeds (this is their official testing utility that I use to erase the flash):

Before using your program, I was using esptool cli with 1.5Mbps setting: it was fast and reliable on those devices.

esptool.exe -b 1500000 write_flash 0x0 tasmota32-core2.factory.bin

This is the log from ESP-Flasher: it tries 460800 but it doesn't work, so it goes back to 115200.

It would be really nice if it could test more speed rates when autodetecting, and/or have an option to choose Auto, vs manual speed rates.

Using 'COM3' as serial port.
Connecting....
Detecting chip type... Unsupported detection protocol, switching and trying again...
Connecting....
Detecting chip type... ESP32
Connecting....

Chip Info:
 - Chip Family: ESP32
 - Chip Model: ESP32-PICO-D4 (revision v1.0)
 - Number of Cores: 2
 - Max CPU Frequency: 240MHz
 - Has Bluetooth: YES
 - Has Embedded Flash: YES
 - Has Factory-Calibrated ADC: YES
 - MAC Address: E8:9F:6D:09:63:C0
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Chip does not support baud rate 460800, changing to 115200
Connecting....
Detecting chip type... Unsupported detection protocol, switching and trying again...
Connecting....
Detecting chip type... ESP32
Connecting....
Uploading stub...
Running stub...
Stub running...
 - Flash Size: 4MB
 - Flash Mode: dio
 - Flash Frequency: 80MHz
Erasing flash (this may take a while)...
Chip erase completed successfully in 2.7s

Trying to install the Tasmota firmware. Got a 404 error within the log output of this program:

...
 - Flash Size: 4MB
Unexpected error: Error while retrieving firmware file 'https://raw.githubusercontent.com/Jason2866/ESP_Flasher/factory/bootloader/esp32/bin/bootloader_dout_40m.elf': 404 Client Error: Not Found for url: https://raw.githubusercontent.com/Jason2866/ESP_Flasher/factory/bootloader/esp32/bin/bootloader_dout_40m.elf

Details

• Windows 10
• Installed via pip

I'm trying to run ESP-Flasher-Windows-x86.exe on a win-7 32-bit PC and I immediately get the message "The program can't start because api-ms-win-core-path-l1-1-0.dll is missing from your computer." Using the program "Everything" to search for files, I see that I have many "api-ms-win-core-" files but no "api-ms-win-core-path-" files. When I dismiss the error message a second message comes up - Error loading Python DLL - and then it shows a path to a file called python39.dll. That file does indeed exist at the given path. The PC in question does have python 3.7 installed (I believe it is the last version that will run on windows 7) but I don't know if that's a factor here.

Hi,

I bought an ESP-30 CAM device with the built-in USB interface (on aliexpress, seems to be on amazon too):

I downloaded tasmota32-webcam.bin from http://ota.tasmota.com/tasmota32/release/ and flashed it to my device using ESP Flasher on Windows 10 x64.

Unlike many tutorials I saw, I had to press the "Flash" hardware button while pressing "Flash ESP" on the software, but I had the same results by wiring IO0 to GND.

Here is the output. As you can see, the logs don't show:

Using 'COM5' as serial port.
Connecting........
Detecting chip type... ESP32
Connecting...

Chip Info:
 - Chip Family: ESP32
 - Chip Model: ESP32-D0WDQ6 (revision 1)
 - Number of Cores: 2
 - Max CPU Frequency: 240MHz
 - Has Bluetooth: YES
 - Has Embedded Flash: NO
 - Has Factory-Calibrated ADC: YES
 - MAC Address: 10:52:1C:64:32:D8
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
 - Flash Size: 4MB
 - Flash Mode: qio
 - Flash Frequency: 80MHz
Erasing flash (this may take a while)...
Chip erase completed successfully in 2.7s
Flash params set to 0x002f
Compressed 18656 bytes to 12053...
Writing at 0x00001000... (100 %)
Wrote 18656 bytes (12053 compressed) at 0x00001000 in 0.3 seconds (effective 549.3 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 129...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (129 compressed) at 0x00008000 in 0.0 seconds (effective 4034.9 kbit/s)...
Hash of data verified.
Compressed 8192 bytes to 47...
Writing at 0x0000e000... (100 %)
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.0 seconds (effective 15296.5 kbit/s)...
Hash of data verified.
Compressed 1425152 bytes to 832040...
Writing at 0x00010000... (1 %)
Writing at 0x00014000... (3 %)
Writing at 0x00018000... (5 %)
Writing at 0x0001c000... (7 %)
Writing at 0x00020000... (9 %)
Writing at 0x00024000... (11 %)
Writing at 0x00028000... (13 %)
Writing at 0x0002c000... (15 %)
Writing at 0x00030000... (17 %)
Writing at 0x00034000... (19 %)
Writing at 0x00038000... (21 %)
Writing at 0x0003c000... (23 %)
Writing at 0x00040000... (25 %)
Writing at 0x00044000... (27 %)
Writing at 0x00048000... (29 %)
Writing at 0x0004c000... (31 %)
Writing at 0x00050000... (33 %)
Writing at 0x00054000... (35 %)
Writing at 0x00058000... (37 %)
Writing at 0x0005c000... (39 %)
Writing at 0x00060000... (41 %)
Writing at 0x00064000... (43 %)
Writing at 0x00068000... (45 %)
Writing at 0x0006c000... (47 %)
Writing at 0x00070000... (49 %)
Writing at 0x00074000... (50 %)
Writing at 0x00078000... (52 %)
Writing at 0x0007c000... (54 %)
Writing at 0x00080000... (56 %)
Writing at 0x00084000... (58 %)
Writing at 0x00088000... (60 %)
Writing at 0x0008c000... (62 %)
Writing at 0x00090000... (64 %)
Writing at 0x00094000... (66 %)
Writing at 0x00098000... (68 %)
Writing at 0x0009c000... (70 %)
Writing at 0x000a0000... (72 %)
Writing at 0x000a4000... (74 %)
Writing at 0x000a8000... (76 %)
Writing at 0x000ac000... (78 %)
Writing at 0x000b0000... (80 %)
Writing at 0x000b4000... (82 %)
Writing at 0x000b8000... (84 %)
Writing at 0x000bc000... (86 %)
Writing at 0x000c0000... (88 %)
Writing at 0x000c4000... (90 %)
Writing at 0x000c8000... (92 %)
Writing at 0x000cc000... (94 %)
Writing at 0x000d0000... (96 %)
Writing at 0x000d4000... (98 %)
Writing at 0x000d8000... (100 %)
Wrote 1425152 bytes (832040 compressed) at 0x00010000 in 18.8 seconds (effective 607.0 kbit/s)...
Hash of data verified.

Leaving...
Hard Resetting...
Done! Flashing is complete!

Showing logs:

If I click on "View Logs", I get this error:

Using 'COM5' as serial port.
Unexpected error: could not open port 'COM5': PermissionError(13, 'Accès refusé.', None, 5)

Of course, there was never any Tasmota hotspot available, I checked at every step.

If I reset the device (without IO0 wired to GND), I get logs that are sometimes unreadable (like if the baudrate was off) and the device seems to reboot every second. I can obviously not check the output with a better power source than my computer USB, but the device seems to reboot with a powerful (3A) source as well, and it doesn't provide more wifi hotspot.

Here are an example of (readable) log output:

I tried with different cables and different COM ports with the same effect. I also tried the older release that was used in the tutorial (v9.3.1, the current version is v9.5.0).

Is there any chance this might come from ESP Flasher?

Firefox 121.0.1 flags the current Windows.exe build as malware.
Applies to all .exe versions back in time.
Virustotal.com analysis -