...and i have a similar problem with my R3 nano clone.
Also tried other bootloader. Can't change port because IDE does not detect a Arduino board. Only the standard blinking sketch with blinking L led but no connection to upload (and yes pc detects a device). Sketch uses 2034 bytes (6%) of program storage space. Maximum is 30720 bytes. Global variables use 188 bytes (9%) of dynamic memory, leaving 1860 bytes for local variables. Maximum is 2048 bytes. avrdude: ser_open(): can't open device "\.\COM3": Het systeem kan het opgegeven bestand niet vinden.
Failed uploading: uploading error: exit status 1
I also have a normal size R3 and this one works perfect.
Now if i stick the Nano in the pc via usb no more blinking L led.
But: pc and IDE see there is a device connected but IDE can't upload sketch (sorry don't have pc with me to show error).
I removed the ch340 driver (i should be this one because the board is with the ch340 usb chip) ans installed the (older) friver from the Sparkfun website. No succes
Although i can set the right com port now (and select nano in IDE) the tx and rx led's don't start flickering when the IDE starts uploading sketch to board (it just keeps uploading without result).
I'll try some other stuff i read i could remedy the problem but i'm not at home now.
-removing ch340 driver without re install and plugging nano in so new driver get's installed automaticly
-try other USB cable
-plug board in to other usb port
-...
-buying a Sparkfun or Seeed Nano board
Finaly solved.
Bit suspicious because the standard installed blink sketch did not work anymore (bootloader bricked?).
First tried other usb ports (and erasing).
Then other usb cable.
Then uninstalling and re-installing the ch340 driver (this time the widows/microsoft version) and aha...IDE recognizes port AND nano board automatically.
but...still won't upload sketch.
Then grabbed my uno and used it again as programmer and...voila, bootloader re-installed So this time it works. Cause???
Then tried uploading sketch in nano with success!
thx everybody! ...everything points at a faulty bootloader but it's a mystery why re-loading the bootloader did not work yesterday.