Hi @jahir323. I don't have any experience with "ArduinoDroid", but I know that it has one configuration for the official (and faithful clone) Nano boards that have an FTDI FT232R USB chip, and another configuration for the common cheap Chinese Nano derivative boards that instead have the WCH CH340 chip. So it is possible that this error could be caused by having ArduinoDroid configured for the FTDI chip when your board actually has the CH340 chip instead.
I see that there is an "internal" uploader that is claimed to be more reliable and automagically determines which USB chip your board has:
So configure ArduinoDroid to use that "internal" uploader and then try uploading to your board again. Hopefully it will be successful after you do that.
The manufacturer of the Nano board uploads a program to the board that blinks the LED at the factory. The blinking LED provides an indication that the board has at least basic functionality.
When you upload an Arduino sketch to the board, that factory blink program will be replaced and the board will then behave according to whatever code was in the sketch you uploaded. If that code doesn't blink the LED, then the LED will stop blinking after you successfully upload the sketch program to the board.
So forget about the blinking LED and focus on fixing the error that occurs when you try to upload to the board.