ESP32-WROVER and ESP32-WROVER-I are first generation 1.8v ESP32-WROVER-B and ESP32-WROVER-IB are second generation 3.3v ESP32-WROVER-E and ESP32-WROVER-IE are third generation 3.3v I don't know if running at wrong vddsdio voltage may contribute to your problems. I think you need to wait for espressi...

Isn't wrover-i supposed to be bootstrapped to 1.8v or did you set efuse? Is it first generation wrover or B or E version?

Did you dump the flash? Did you try reprogramming? Did you check flash status registers?

Is this a different design than your other thread with boot failure?

Why should gpio0 have 1.8v?

Afaik the only way to exit stuck state is to pull en pin low until voltage is good.

You have a different flash chip than the GitHub issue and seems your problem is different so you will have to wait for espressif to examine your hardware.

Using emulated efuse is going to result in faking the encryption. You can only turn on the actual hardware encryption by burning the efuse.

Well then you can sign and flash new apps and bootloaders.

You could use a wake stub or custom bootloader

If you enabled reflashable you should have the keys from when you flashed the other app or did you delete them?