I've got a hold of a bricked 1043NDv2 to try to fix and to add to my network. It was put up on FB Marketplace as junk parts for almost free. I've tried the TFTP "Holding Reset" button on TP-Link Devices, but it does not initialize. It's almost as if the reset button does nothing since there isn't a change of any LEDs. It always lights up as Power, Activity (the one that looks like *), LAN1, and the WPS button. Wireshark does not capture any packets with useful information.
I've soldered a serial header on and have successfully gotten a log to show up on PuTTY. It shows:
U-Boot 1.1.4 (Jun 13 2014 - 15:14:01) ap135 - Scorpion 1.0DRAM: sri Scorpion 1.0 ath_ddr_initial_config(211): (16bit) ddr1 init tap = 0x00000002 Tap (low, high) = (0xaa55aa55, 0x0) Tap values = (0x8, 0x8, 0x8, 0x8) 4MB
Which I know is already different from the Wiki, given that it should be like this:
U-Boot 1.1.4 (Jul 17 2015 - 14:31:22) ap135 - Scorpion 1.0DRAM: sri Scorpion 1.0 ath_ddr_initial_config(178): (16bit) ddr2 init tap = 0x00000003 Tap (low, high) = (0x0, 0x1e) Tap values = (0xf, 0xf, 0xf, 0xf) 64 MB
From then on in, it does nothing apart from normal - lighting up the following LEDs again: Power, Activity (the one that looks like *), LAN1, and the WPS button. I cannot do the standard wait and type
I got a chat with the owner of the bricked router and he stated that he played around with generating his own OpenWRT image and it all went to crap when he installed an image he generated that had ASLR on. Could this have done something to Uboot-Env?
My question is this: Am I missing something? Can I do anything else besides JTAG or reprogramming the SPI/Flash Chip? I don't think that it's worth the effort doing either option since I don't have a fine enough solder tip or the steady hands required for finer soldering if that's the case.