It really depends on what sniffing means in your case. In the 433 MHz band, the traffic you want to sniff must be using some modulation mechanism that you want to target. Suppose the traffic is just OOK type (RC cars, home appliance remote control, etc), then you will need an OOK receiver (433 MHz),...

The question is not very clear. Do you want to connect an 8GB USB flash drive to the ESP32 to read its contents?
Or do you have 8GB flash/SD connected to the ESP32 and need to access that via USB (i.e. make ESP32 act as a USB mass storage device)?

Ohh okay, I thought you did not have OTA on current firmware. The link posted by WiFive above is a good place to start then. You can try overwriting the bootloader and partition areas on another board where you have UART download enabled. Once you get that working, you can do the same with the board...

Isn't that an eFuse setting? Last I checked the eFuse was OTP memory, so if you set something in there that you did not want to, then you bricked the board.

I cannot answer this without having information on your hardware (i.e. what is accessible physically and what is not). If your board is in a product that the end user is using and can only access a USB connector to re-flash the board, that can be tough. Do you have access to the EN line via a reset ...

You can either modify the AT command firmware to add custom AT commands that extremely simplify what you want to do by handling all the APIs directly, or you need to issue AT commands and handle everything at a lower level (like setting up a connection, forming and parsing all the data uploaded and ...

I have faced something like this before, are you using an RS485 transceiver with direction control pin?

Looks like incorrect flash setting to me. I have blogged about this error, it is kinda common:
https://pcbartists.com/firmware/esp32-f ... op-solved/

Are you using a WROOM module with more than 4MB flash?

Are you talking about the "footage" as in video, or do you just want to capture raw photos like a DSLR does? RAW format photos are basically just the uncompressed sensor matrix data + associated settings used to capture that data. So if you are running the OVxxxx sensor in non-JPEG mode, you are bas...

In my experience this is not realistic. The response time (time from interrupt source changing to user ISR execution) is around 2 us. That time is not exactly the same either, it seems to change every time with some variance. For your application, it would be best to hook up an STM32 or something (c...