Tried flashing (flash3) but didn't work, tried undoing, now device unresponsive - Tonbux switch

I’m kinda freaking out. I successfully flashed the middleware firmware, got this info:

READ FLASH: http://10.42.42.42/get?read=HEX-ADDRESS
ChipID: 258c75
MAC: 3C:71:BF:25:8C:75
SdkVersion: 1.5.3(aec24ac9)
BootVersion: 4
BootMode: 1
FlashMode: 1M QIO @ 40MHz
FlashChipId: 1440c8
FlashChipRealSize: 1048576
FlashChipSize: 1048576
FlashChipMode: 0
system_upgrade_userbin_check: user2 0x81000

Then I did curl http://10.42.42.42/flash3. It said Device should flash http://10.42.42.1/files/thirdparty.bin and restart. But the device didn’t restart, it just stayed connected to the vtrust-flash and the “sonoff-xx” AP never came up.

I waited an hour, and then did curl http://10.42.42.42/undo to try again. It said it would undo and restart, and the device disconnected from vtrust-flash but never turned back on. Now I can’t get it to turn on at all.

[melyux]

@onebyside @AlphaDE – Got the first one flashed as well using the serial ports with the Raspberry Pi Zero. Nice! Both have Tasmota now. I realized the first failure never managed to backup the factory firmware. Perhaps some sort of Wi-Fi connection issue with the vtrust-flash AP on the Pi Zero the first time around.

[kueblc]

There was a bug in the intermediate firmware that caused undo to fail if you were already booting from userspace 1. I believed this to be related to the problems you reported, but the bug is now fixed in the current master. I have found identical devices from the same box that boot from different userspaces so it’s entirely possible that you just happened to undo on one of the devices that booted from 1.

I have not gotten any other reports of corruption but if you have any data I would be happy to look into it.