R7000 bricked during update cannot recover.

> 15613922886085217141556636394889.jpg

   First, find out how to do copy+paste from a Command Prompt window, or
else how to do a screen grab on Windows.  Your photo cropped off the
useful part of the file name.

> [...] But after it says "transfer successful: 224 bytes in second(s),
> 224 bytes/s" nothing happens to the router it just keeps power blinking
> led.

   What I see is, "Transfer successful: 224 bytes in 1 second(s), 224
bytes/s".  But you were close.

   To me, that looks like the TFTP scheme is working, but 224 bytes is
not even close to the size of a firmware image file.  For a popular
recent version, for example:

pro3$ unzip -l R7000-V1.0.9.42_10.2.44.zip
Archive:  R7000-V1.0.9.42_10.2.44.zip
  Length      Date    Time    Name
---------  ---------- -----   ----
 32268346  09-10-2018 13:31   R7000-V1.0.9.42_10.2.44.chk
     3121  10-01-2018 12:26   R7000-V1.0.9.42_10.2.44_Release_Notes.html
---------                     -------
 32271467                     2 files

   So, a typical correct file ("R7000-V1.0.9.42_10.2.44.chk") has a size
of roughly 32MB (not 0.2KB).  I don't know what you sent to the router,
but it seems to have been some small, wrong thing, not the appropriate
".chk" file.

> This is the version that I'm trying to reinstall,
> R7000-V1.0.8.34_1.2.15 [...]

   Why?

> [...] I'm not sure if it can revert to any old firmware. [...]

   I'd expect loading any version to be possible, if you can load some
version.

> [...] I really feel that this is a trash unit, [...]

   Perhaps, but so far there's little evidence that you're trying to
push a real firmware image file at it.