Debricking an old wrt1900acs v2

Hi people.

I have managed to semi brick an Linksys wrt1900acs that I brought back from retirement in order to re-purpose to as an access point in my local bar (micro pub). It's previous use was to act solely as a firewall and a vpn host on my home network. It was previously running an old version of OpenWrt (version 17 I think) and had provided many years of good service. I had disabled the wireless functions to avoid interference my new mesh network.
I unwisely decided to upgrade to the latest release and encountered the image not recognised problem. So I used scp to copy the image to router and then I connect the router directly to my main Linux system and used ssh to login via the lan. I then did forced flash of the image. The result was not good. The router was not fully bricked. Ports 2, 3 and 4 showed lights when the cable lan cable from the pc was plugged in. Port 1 did not. Ports 2, 3 and 4 did not respond to arp requests for any of the addresses I thought the router may have been configured with.
My next step was to connect a serial cable to the router (I had already fitted a stereo jack to enable access to the serial header). One power cycling the router the results were mixed. They showed that the router was booting the kernel but stopping before putting up a login prompt. The output from the router also contained quite a few lumps of random garbage.

This is the final few lines of the boot sequence.

j\V^[   16.805961] ieeu&m\Z^L'(XK5{[   16.812343] ieee80211 phy1: a a a a a a a a a a a a 0 0 0 0 
[   16.818793] ieee80211 phy1: Channel: 12: 0x0 0@pf
[   16.823795] ieee80211 phy1: a a a a a a a a a a a a 0 6  16.829485] ieee80211 phy1: Channel: 13: 0x0 0x0 0xf
[   16.834486] ieee80211 phy1: a a a a a a a a a a a a 0 0 0 0 
^}\\_[   16.840191] ieee80211 phy0: regdomain: ETSI
[   16.844820] ieee80211 phy0: Channel: 36: 0xlC+lHL�"/?kR+LHL855507] ieee80211 phy0: Channel: 40: 0x0 0x0 0xf
[   16.860496] ieee80211 phy0: d d d d d d d d e e e e e e e e 
[   16.866197] ieee80211 phy0:Y[5{nr���"###333?*/?***jRR�JR�J""""""""*****
*jR[   0&.887573]nH^Channel: 52: 0x0 0x0 0xf
\[   16.887585] ttyS ttyS0: 1 input overrun(s)
[   16.892570] ieee80211 phy0: d d d d d d d d e e e e e e e e 
[   16.892573] ieee80211 phy0: Channel: 56: 0x0 0x0 0xf
[   16.892577] m|nH^d d d d d d d d e e e e e e e e 
[   16.892580] ieee80211 phy0: Channel: 60: 0x0 0x0 0xf
[   16.892584] ieee80211 phy0: d d d d d d d d e e e e e e e e 
[   16.930071] ieee80211 phy0: d d d d d d d d e e e e e e e e 
[   16.935758] ieee80211 phy0: Channel: 100: 0x0 0x0 0xf
[   16.940832] ieee80211 phy0: d d d d d d d d e e e e e e e e 
TuT[   16.946517] ieee8ZL'(XK5{nrK�"3"""#"*++++/*R+$HHL)O5RnR)�J"""""""*******R�$5{WWmr""""""""*****///RlrK
D5RR)�J"3#33wRH+lHL)�B05J~*HHL)"#""##"#*+**+*/jRrJ0!R&S)VVf d d dd d e e e e e e e e 
[   17.011969] ieee80211 phy0: Channel: 128: 0x0 0x0 0xf
[   17.017046] ieee80211 phy0: d d d d d d d d e e e e e e e e 
[   17.022732] ieee80211 phy0: Channel: 132: 0x0 0x0 0xf
[   17.02D"?/Rr2T  DYC+HHL�J""#"""""********jRR&S)VVdr�"333/??/RrO"L.060079] ieee80211 phy0: d d d d d d d d e e e e e e e e 
u}v   #B
        c_cBJbBBBBBBBBBY T}UU^uY}]\YX}\]YYwugoY] ^]~Ty ] ][   17.386168] IPv6: y<NEVEEV_CHANGE): br-lan: link becomes ready

Has anyone got any ideas what is going on here?
Is it fixable?
How do I go about about it?

All help will be gratefully received.

Thanks

Roger

Start by resolving what looks like a TTL serial connection issue. Since you appear to have that (albeit with issues), you should be able to just tftp image(s) to device. Current stable runs fine.

Fixed the ttl serial problem by direct wire wrap on the relevant pins. Works fine now. Can get into the shell prompt.

Just got to resolve why I cannot get in by ssh.