BK7231N sensor recovery after wrong flash UA 1.18.288 (no bootloader)

The sensor is the same as in this post: https://www.elektroda.com/rtvforum/topic4130528.html.
I inspire from here for my first firmware flash.
Thank you! I appreciate all your work!

First, I flashed it successfully, using wires BK7321 Easy UART Flasher.
The firmware was OpenBK7231N_QIO_1.18.287.
After I got access to the AP/Web interface, I upgraded it with OpenBK7231N_1.18.287_hlw8112.rbl (because I needed the hlw8112 library).
Everything was fine; it works OK!
The only small problem is that I have no access to calibration commands...

Then I decided to re-flash it, using the same wires and Flasher BK7321.
But by mistake, I chose the wrong firmware, OpenBK7231N_UA_1.18.288_hlw8112.bin (

UA

type, instead of

QIO

). I didn't know that this firmware type (UA) is not appropriate for UART flashing and could overwrite the original bootloader (it starts flashing from the 0x000 address).
Unfortunately I checked "Ignore CRC error".

Then, I tried to "Restore RF Parts", but with no success.

Please tell me if there is any method to get my sensor alive again (restore Bootloader).
Thank you!
What is the exact brand/model of the sensor (or can you link/name the “same as in this post” device), so people can check the correct bootloader/layout for that board?
Tuya WiFi Energy Meter PM01_A002 [CBU][BK7231N] HLW8112
Same as in this post: https://www.elektroda.com/rtvforum/topic4130528.html
What happens now when you connect it again with BK7231 Easy UART Flasher—does it still detect the chip, and if yes, what exact output/error messages do you get?
The chip is detected by the flasher, I can write firmware, with no errors.
But after writing successfully, the sensor did not boot - the "OPENBK...." AP didn't bring up.

Just write QIO firmware with "Overwrite bootloader" checkbox checked in.

>>21901471 But on the BK7231 Flasher, it's mentioned "For N/M don't use it".
Is it safe to use this?

>>21901481
I don't remember where that remark came from, but it' safe for most N/M chips.
On T, U and 7252 it would result in a hard brick, but not on N/M.
It' likely that this warning came for vendor-encrypted BK7231N's. On those, if bootloader is erased/replaced, there's little hope to get their specific encryption keys, unless there's a backup available.