KC686-A6 error on upload

[sm4l]

Hi everyone, I'm having trouble uploading data to my KinCony KC868-A6 v1.3SP board and would really appreciate some help.
This morning I got home and, to my disappointment, the board wasn’t working. I finally had time to try uploading my firmware again, but it’s not working.

• The board’s LED is on as usual.
  
• The USB connection is recognized by my computer.
  
• However, in the SPDownload tool, the board info doesn’t appear — it seems like it’s not being detected properly.
  
• I’ve tested four different USB cables (all confirmed to work for data transfer on my Samsung smartphone).
  
• I don’t have any sensors connected to the board right now.
  
• There were no power surges or electrical issues today, so I doubt the ESP32 is fried.
  

Has anyone experienced something similar or have any ideas on what I can try to fix this?
Thanks in advance!


UPDATE:

Code:

PS D:\Downloads\DEV KC686-A6\KCS_KC868_A6_V2.2.12> python -m esptool --chip esp32 --port COM7 erase_flash
esptool.py v4.8.1
Serial port COM7
Connecting....
Chip is ESP32-D0WD-V3 (revision v3.1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 2c:bc:bb:bf:69:5c
Uploading stub...
Running stub...
Stub running...
Erasing flash (this may take a while)...
Chip erase completed successfully in 0.0s
Hard resetting via RTS pin...
PS D:\Downloads\DEV KC686-A6\KCS_KC868_A6_V2.2.12> python -m esptool --chip esp32 --port COM7 --baud 115200 write_flash 0x0 KCS_KC868_A6_V2.2.12.bin
esptool.py v4.8.1
Serial port COM7
Connecting....
Chip is ESP32-D0WD-V3 (revision v3.1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 2c:bc:bb:bf:69:5c
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Flash will be erased from 0x00000000 to 0x001f4fff...
Compressed 2049248 bytes to 776667...
Wrote 2049248 bytes (776667 compressed) at 0x00000000 in 68.0 seconds (effective 241.1 kbit/s)...
File  md5: dca5832fce0deaae24a324e292f9835d
Flash md5: f0930babe06a54de41f91c7b9e0ece89
MD5 of 0xFF is b4b16439163a7c79fe686aebc65ec0b9

A fatal error occurred: MD5 of file does not match data in flash!

With erase the and flash, the board started to work again.  but i cant update any config on web server. 
i cant flash with ESP32 DOWNLOAD TOOL. 

the error occours.

[admin]

take a photo of your pcb, how you wire.

[sm4l]

take a photo of your pcb, how you wire.

here.

the commands is working, but if i try to on 3 relay, the board restart. lost connection and up again.

[admin]

what power supply you are using? 12V how many current A?

[sm4l]

what power supply you are using? 12V how many current A?

12V 2A . The supply of an NUC .

   here is log with tasmota install 

Code:

rst:0x3 (SW_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:6656
load:0x40078000,len:15052
load:0x40080400,len:3836
entry 0x4008069c
I (52) boot: ESP-IDF v4.4.7-dirty 2nd stage bootloader
I (53) boot: compile time 12:46:57
I (53) boot: Multicore bootloader
I (57) boot: chip revision: v3.1
I (61) boot.esp32: SPI Speed      : 40MHz
I (66) boot.esp32: SPI Mode       : DIO
I (70) boot.esp32: SPI Flash Size : 4MB
I (75) boot: Enabling RNG early entropy source...
I (80) boot: Partition Table:
I (84) boot: ## Label            Usage          Type ST Offset   Length
I (91) boot:  0 nvs              WiFi data        01 02 00009000 00026000
I (98) boot:  1 phy_init         RF data          01 01 0003f000 00001000
I (106) boot:  2 factory          factory app      00 00 00040000 003b0000
I (113) boot: End of partition table
I (118) esp_image: segment 0: paddr=00040020 vaddr=3f400020 size=fe9d0h (1042896) map
I (504) esp_image: segment 1: paddr=0013e9f8 vaddr=3ffb0000 size=01620h (  5664) load
I (506) esp_image: segment 2: paddr=00140020 vaddr=400d0020 size=a2c70h (666736) map
I (751) esp_image: segment 3: paddr=001e2c98 vaddr=3ffb1620 size=01d7ch (  7548) load
I (754) esp_image: segment 4: paddr=001e4a1c vaddr=40080000 size=0fa9ch ( 64156) load
E (783) esp_image: Checksum failed. Calculated 0x5c read 0x58
E (783) boot: Factory app partition is not bootable
E (783) boot: No bootable app partitions in the partition table
ets Jul 29 2019 12:21:46

It's possible i erased the bootloader and table partitions? how can i recovery it?

[admin]

you can try to download KCS firmware again. or you can download firmware by ESPHome yaml file.
Do you problem is can't turn on 3 relays at the same time? can you take a video of your problem, send to WhatsApp number: +86-15381188302

[sm4l]

you can try to download KCS firmware again. or you can download firmware by ESPHome yaml file.
Do you problem is can't turn on 3 relays at the same time? can you take a video of your problem, send to WhatsApp number: +86-15381188302

after several attemps the firmware stoped working.
i think the ESP is broken ...


Firmware Upload Failure

• Tools Used: PlatformIO / esptool / Arduino IDE
  
• Error Message:
  
  Code:

  A fatal error occurred: MD5 of file does not match data in flash!
• This indicates the upload process finishes, but the board fails validation after flashing.
  

2. ESP32 Not Responding Post Upload
[*]Upload process starts but either:
Fails at checksum.
Uploads successfully only esptool via cli.

Code:

rst:0x10 (RTCWDT_RTC_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:6656
load:0x40070000,len:15052
load:0x40080400,len:3836
csum err:0xfe!=0xf8
ets_main.c 384
---- Closed the serial port COM6 ----