I have seen a lot of people having same type issue I am with sketch messing up NANO ESP32, and re-flashing bootloader does not return it to "Genuine Arduino ESP32" It thinks its "Ozobot esp32" , and programming and serial behaves differently then it did a week ago when I took it out of the box.
I saw reference to a 9 step process, but have not found it.
Thanks
Ed
I found this document on the official Arduino site:
Hopefully it will be of some help?
Thank you, but no improvement. I have done this procedure 9 times already, and It still does not restore the DFU functionality to this board. I can upload sketches using the esp tool mode, but it then jumps from Com13 to com12 when it resets.
Is the Ozobot identification still persisting?
What's happening with the LEDs?
I once posted an eleven step recovery process, be aware that during this process the COM port number can change and is quite normal so keep an eye on the port number in "Tools" every step of the way.
Nano ESP32 Bricked? - #3 by sumguy.._gaMTkyOTA4NTQzMy4xNzkxMjEwMzI1*_ga_NEXN8H46L5*czE3OTEyMTAzMjUkbzEkZzAkdDE3OTEyMTAzMjUkajYwJGwwJGg2MDQ5NDIzMjE.
@n3sdoham which operating system are you using?
Yes. Purple on boot up / reboot cycle. Green when I wire b1 to gnd.
Windows 10. AMD CPU, Asrock X370 gamer motherboard.
Its seems that some part of the Ozboot stuff is not getting cleared.
You could try manually erasing the flash first.
python -m esptool --chip esp32s3 erase_flashAfter that run the process linked in post #2 to re-install the bootloader again.
If that doesn't do it, then I'm not sure what else to suggest.
BitSeeker, you are the winner! This has gotten my board straightened out, back to booting properly, and downloading code via DFU on com 13 and the serial port not crashing! Yay!
Brilliant!! Glad you got it working again. 