@teastain2 absolutely lacks. That's because I'm getting the write timeout messages,
To put it short, I think my brand new board is defective. I kind of worked for a while, at least the screen. Nut now I just plugged in the other board (I bought two) and finally I understand why it's called "touch". If I touched the first board I tried never happened anything. This one works.
My theory is that it had a small defect at the beginning and then it got worse as I took in in my hands, plugged in, unplugged, etc.
The smaller (narrower) ribbon wire that goes from the board to the screen (perhaps the touch cable?) is suspicious.
Now the question is, how do I get the screen off to check the wiring?
(Oh btw, sometimes I saw "check your wiring" error messages too!)

Confirmed. I could get the display off the board without damaging it and it was instantly clear that this cable isn't attached: https://imgur.com/a/iql0GXk

I put the cable back, and nothing changed. Write timeout.
Then I disconnected both cables - to try just the board alone with no screen. Write timeout.
Then I went as low as 9600, then 1200 bits per second. Write timeout.

So the board is brand new, it worked for a few days. My theory is that when that cable began to get loose, it badly one of the examples I uploaded. Now it's generating a ton of errors I can see in serial monitor. A permanent storm of errors. It renders the CPU so busy that it can't respond to serial, just pushes out the errors.

So I'd need a hard reset pin, that can wipe the entire memory of the board. Any hints would be appreciated.

Yeah, the smaller flat ribbon cable is loose. Detached from the connector. Anybody knows how to detach the screen from the board itself?

@teastain2 absolutely lacks. That's because I'm getting the write timeout messages,
To put it short, I think my brand new board is defective. I kind of worked for a while, at least the screen. Nut now I just plugged in the other board (I bought two) and finally I understand why it's called "touch". If I touched the first board I tried never happened anything. This one works.
My theory is that it had a small defect at the beginning and then it got worse as I took in in my hands, plugged in, unplugged, etc.
The smaller (narrower) ribbon wire that goes from the board to the screen (perhaps the touch cable?) is suspicious.
Now the question is, how do I get the screen off to check the wiring?
(Oh btw, sometimes I saw "check your wiring" error messages too!)

@teastain2 tried it, with Arduino IDE too, still dealing with the same "Write timeout" issue.
In the meantime I visited the troubleshooting page and did a couple of checks. The output of esptool looks good to me:

C:\temp>esptool -p COM15 flash_id
esptool.py v4.7.0
Serial port COM15
Connecting...
Detecting chip type... ESP32-S3
Chip is ESP32-S3 (QFN56) (revision v0.2)
Features: WiFi, BLE, Embedded PSRAM 8MB (AP_3v3)
Crystal is 40MHz
MAC: 74:4d:bd:87:80:e8
Uploading stub...
Running stub...
Stub running...
Manufacturer: ef
Device: 4018
Detected flash size: 16MB
Flash type set in eFuse: quad (4 data lines)
Hard resetting via RTS pin...

Tried different USB ports (Type A and C), different cables.
What I'm going to try now is my other Lilygo Amoled board, however I'm a little bit afraid that it'll break it somehow.

@teastain2 anything would help a lot. Thank you.
Platformio just tried to refresh itself and failed, so my Windows env is broken now, but I just tried in Linux and it's the same there. Monitoring works, even the device analysis works, but any attempt to upload fails with a timeout error.

The crazy thing is that in the analysis I can see the source files, even where a potential div by zero error is happening in the lvgl (lowercase) directory in line 570. I suspect this error makes the board so busy it can't respond.

@teastain2 Yes, I'm sure. That's the only logical conclusion since these messages keep pouring in the monitoring window. I just wonder why I get timeout errors every time I try to upload something.

Unfortunately I don't remember which project was it exactly that broke the board. As I said, this was my first time so I just cloned this repo, and started to uncomment different src_dir lines in platformio.ini.

I remember AdjustBrightness worked, however I couldn't use the slider (touch interface didn't seem to work). Lvgl_images also worked, but I couldn't change to another image for the same reason. LVGL_SD_Images also worked but I didn't have an SD card reader so all I could see was an error message. Fair enough. Then I could restore to Factory.

Now things get a bit blurry here because I panicked and tried a whole bunch of stuff to revive my board. Maybe it was the LumenMeter project that actually broke it. Or the LVGL_Rotation one. Not sure. But apart from changing the src_dir, I didn't do anything with the repo.

Started with this board just today. I uploaded the examples from the GitHub repo one by one, but finally I uploaded one that must be incompatible because the screen went blank. Now I can monitor the board but can't upload anything because "A serial exception error occurred: Write timeout".

What I see in the monitor, it comes in an infinite loop:

ELF file SHA256: 6328e98876904dbf

Rebooting...
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0xc (RTC_SW_CPU_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x4205a896
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x44c
load:0x403c9700,len:0xbe4
load:0x403cc700,len:0x2a38
entry 0x403c98d4
[   169][E][LilyGo_AMOLED.cpp:558] beginAMOLED_147(): Failed to find AXP2101 - check your wiring!

assert failed: void beginLvglHelper(LilyGo_Display&, bool) LV_Helper.cpp:84 (buf)


Backtrace: 0x40377f5e:0x3fcebcb0 0x4037b59d:0x3fcebcd0 0x40381dad:0x3fcebcf0 0x4202b5cb:0x3fcebe20 0x42001c20:0x3fcebe40 0x4203146a:0x3fcebe60

Is there a way to get this board back or is it dead?