@ ESP_Sprite, Excellent idea!

You can, but why not just use traces to the bottom side.

I have tested some of the power pins, for the V5 pin, it is giving me 2 volts exactly instead of 5 volts. Even the 3.3 volts pin is giving me like 0.5 volts instead of 3.3 volts. Why is that? Can anyone please explain it to me? What are the possible solutions? I have also tested GPIO pin number 12,...

This information is in the data sheet.

As the old saying goes. There is more than one way to skin a cat. FWIW, it is a basic thing with really the only difference is some switches are more "dirty" than others requiring a longer delay. It also depends on the circuit design as well. Did the user put a cap & pull up/down resistor, and what ...

Well, What I would do next is to create a simple app that toggles module pins 26 (IO4) and 29 (IO5). When you toggle them make sure they are always opposite level from one another. That will help verify a short on the PCB. Verify with a scope that each pin is toggleing and you can move onto the next...

Are you aware of the examples on github ?
You can find some examples in there.
https://github.com/espressif/esp-idf/tr ... eripherals

There is an example in the examples folder for doing just that.

yes, i am aware of the other bootstrap pins. I took his statement to litterally, as if its part of the active flashing process like tx/rx pins But because GPIO2 is involved in the flashing/programming process, Did you go through the DHT12 code to see if the author messed up anywhere ? it seems he wr...

I am more curious why you need GPIO2 to flash your device.
GPIO0 is all that is needed.