EMS-ESP randomly reverts from firmware 3.6.4 back to firmware 3.5.1 about ems-esp32

[MichaelDvP]

esp have 2 program partitions, on update the non-active is written and made active on successfull upload. IIn a intermediate version the ota_data was corrupted, resulting in boot from first partition on every reset.
You can flash with usb, which rewrites the ota_data.
Or upload twice to write both partitions new. Just upload 3.6.5dev15 from running 3.6.5dev15.

[zamojski]

Looks fine after flashing with USB, thanks!

[djvanhelmond]

I flashed with USB, but didn't resolve the issue.
I assumed it was a hardware issue, bought a new S3 and all is working fine now.

[djvanhelmond]

I've just loaded 3.6.5 dev 15 to see if the problem persists.

[zamojski]

I've uploaded the update twice but the issue still persists. Do I really need to flash it with USB? (I thought I was on 3.6.4 already but it seems the issues stays for quite long).

2024-03-25 18:22:18.000 I 1: [emsesp] Last system reset reason Core0: Software reset CPU, Core1: Software reset CPU
2024-03-25 18:22:18.000 I 2: [emsesp] Loading board profile S32
2024-03-25 18:22:18.000 I 3: [system] Current version from settings is 3.6.5-
2024-03-25 18:22:18.000 N 4: [system] Downgrading to version 3.5.1-
2024-03-25 18:22:18.000 I 5: [emsesp] Starting EMS-ESP version 3.5.1 (hostname: ems-esp)
2024-03-25 18:22:18.000 I 6: [dallassensor] Starting Dallas sensor service
2024-03-25 18:22:18.000 I 7: [analogsensor] Starting Analog sensor service
2024-03-25 18:22:18.000 I 8: [emsesp] Loaded EMS device library (113 records)
2024-03-25 18:22:18.000 I 9: [emsesp] Starting Access Point with captive portal on 192.168.4.1

[proddy]

yes, your flash is corrupted and the only way to fix it is a) export settings and any configurations b) flash with USB and c) export back the settings. You're one of the unfortunate people to have a bugged firmware. Sorry about that. But you should be up and running in minutes, provided you have a USB cable