Arduino Nano bricked

Hi all,
I've been working with Arduino Unos for a couple of years now, and I recently decided I wanted to try the Nano V3.0; however, I had troubles with it from the get-go. There were errors on the IDE that I don't remember, but it doesn't matter at the moment because the base point is that the Nano didn't run sketches, and I thought it was bricked. The LED still blinked intermittently, though.
After doing some research, I thought that the bootloader was to blame, and I tried to reinstall it using an Arduino Uno as an ISP interpreter. That, too, has not worked for me to date. I have tried modifying the efuse value for the Nano from 0x05 to 0xFD in the boards.txt file to get rid of a warning, but that did nothing to solve the problem. I also found a cheap CH340 USB-to-Serial chip on the Nano, so I made sure to install that driver.
I am running Arduino 1.6.8 on a Windows 10 64-bit OS. The Nano shows up in my devices as a USB-SERIAL CH340, despite my attempts to install/reinstall the CH340 driver. When I try to upload the bootloader to it through my Uno, the IDE returns this error message:

Arduino: 1.6.8 (Windows 10), Board: "Arduino Nano, ATmega328"

C:\Users\tomba\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6/bin/avrdude -CC:\Users\tomba\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6/etc/avrdude.conf -v -patmega328p -cstk500v1 -PCOM3 -b19200 -e -Ulock:w:0x3F:m -Uefuse:w:0xFD:m -Uhfuse:w:0xDA:m -Ulfuse:w:0xFF:m 

avrdude: Version 6.3, compiled on Sep 12 2016 at 17:24:16
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2014 Joerg Wunsch

         System wide configuration file is "C:\Users\tomba\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6/etc/avrdude.conf"

         Using Port                    : COM3
         Using Programmer              : stk500v1
         Overriding Baud Rate          : 19200
         AVR Part                      : ATmega328P
         Chip Erase delay              : 9000 us
         PAGEL                         : PD7
         BS2                           : PC2
         RESET disposition             : dedicated
         RETRY pulse                   : SCK
         serial program mode           : yes
         parallel program mode         : yes
         Timeout                       : 200
         StabDelay                     : 100
         CmdexeDelay                   : 25
         SyncLoops                     : 32
         ByteDelay                     : 0
         PollIndex                     : 3
         PollValue                     : 0x53
         Memory Detail                 :

                                  Block Poll               Page                       Polled
           Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
           ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
           eeprom        65    20     4    0 no       1024    4      0  3600  3600 0xff 0xff
           flash         65     6   128    0 yes     32768  128    256  4500  4500 0xff 0xff
           lfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           hfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           efuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           lock           0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
           signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00

         Programmer Type : STK500
         Description     : Atmel STK500 Version 1.x firmware
         Hardware Version: 2
         Firmware Version: 1.18
         Topcard         : Unknown
         Vtarget         : 0.0 V
         Varef           : 0.0 V
         Oscillator      : Off
         SCK period      : 0.1 us

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0x1e950f (probably m328p)
avrdude: erasing chip
avrdude: reading input file "0x3F"
avrdude: writing lock (1 bytes):

Writing | ################################################## | 100% 0.01s

avrdude: 1 bytes of lock written
avrdude: verifying lock memory against 0x3F:
avrdude: load data lock data from input file 0x3F:
avrdude: input file 0x3F contains 1 bytes
avrdude: reading on-chip lock data:

Reading | ################################################## | 100% 0.01s

avrdude: verifying ...
avrdude: 1 bytes of lock verified
avrdude: reading input file "0xFD"
avrdude: writing efuse (1 bytes):

Writing | ################################################## | 100% 0.01s

avrdude: 1 bytes of efuse written
avrdude: verifying efuse memory against 0xFD:
avrdude: load data efuse data from input file 0xFD:
avrdude: input file 0xFD contains 1 bytes
avrdude: reading on-chip efuse data:

Reading | ################################################## | 100% 0.01s

avrdude: verifying ...
avrdude: 1 bytes of efuse verified
avrdude: reading input file "0xDA"
avrdude: writing hfuse (1 bytes):

Writing |  ***failed;  
################################################## | 100% 0.06s

avrdude: 1 bytes of hfuse written
avrdude: verifying hfuse memory against 0xDA:
avrdude: load data hfuse data from input file 0xDA:
avrdude: input file 0xDA contains 1 bytes
avrdude: reading on-chip hfuse data:

Error while burning bootloader.
Reading | ################################################## | 100% 0.01s

avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x0000
         0xde != 0xda
avrdude: verification error; content mismatch

avrdude done.  Thank you.

Thanks to anyone who knows how to help!

I don't think you need to worry about reloading the driver if the CH340G chip works. Do the loop back test described in one of the pinned posts at the top of the forum to verify it works ok.

Regarding burning the bootloader, I recommend trying version 1.6.5 or 1.6.12 or 1.6.13 of the IDE. And check that the wiring between the Uno and Nano has good connections. Check that you can boot load one of your other boards such as an Uno.

Loop back test is one of the pinned posts on the Installation & Troubleshooting section of the forum.