Unbrick TP-Link WR1043ND v4

[chrischn82]

Hey guys!

I recently bricked my 1043nd v4 by trying to reflash from working OpenWRT to original TP-Link-Firmware.

I build a serial cable and got some output from "bootloader" (?)

U-Boot 1.1.4 (Jun  7 2016 - 15:56:08)

ap152 - Dragonfly 1.0

DRAM:  64 MB
Top of RAM usable for U-Boot at: 84000000
Reserving 363k for U-Boot at: 83fa4000
Reserving 192k for malloc() at: 83f74000
Reserving 44 Bytes for Board Info at: 83f73fd4
Reserving 36 Bytes for Global Data at: 83f73fb0
Reserving 128k for boot params() at: 83f53fb0
Stack Pointer at: 83f53f98
Now running in RAM - U-Boot at: 83fa4000
Flash Manuf Id 0xef, DeviceId0 0x40, DeviceId1 0x18
flash size 16MB, sector count = 256
Flash: 16 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Net:   ath_gmac_enet_initialize...
No valid address in Flash. Us.ing fixed address
ath_gmac_enet_initialize: reset mask:c02200
athr_mgmt_init ::done
Dragonfly  ----> S17 PHY *
athrs17_reg_init: complete
SGMII in forced mode
athr_gmac_sgmii_setup SGMII done
: cfg1 0x80000000 cfg2 0x7114
eth0: 00:03:7f:09:0b:ad
eth0 up
eth0
Setting 0x181162c0 to 0x20402100
is_auto_upload_firmware=0
Autobooting in 1 seconds
## Booting image at 9f020000 ...
   Uncompressing Kernel Image ... Stream with EOS marker is not supportedLZMA ER
ROR 1 - must RESET board to recover▒▒

i´m not able to break the loop by entering anything.

I know, the device is not worth much anymore, but my heart can not throw away working hardware..
Can someone give me a little advise ?
I am also wondering, the working baudrate is 128000 baud.

[frollic]

you've already tried https://openwrt.org/toh/tp-link/tl-wr1043nd#flashingrecovery_using_tftp_only_without_serial_console ?

[chrischn82]

i´ll try now...

[chrischn82]

@frollic thanks!

It worked with Open-TFTP Server on 192.168.0.66

Now: I tested, what i wanted to test 2 months ago..
Hardware NAT works much faster on TP-Link-Software with about 450 MBit Speedtest. (I´ve got 500 MBit by provider)
With OpenWRT i got about 180MBit or less...(with flow offloading enabled)

Any ideas, (again )

[frollic]

hw offloading not made public by Qualcomm, when the hw support for the SoC was added to Linux.
AFAIK that switch have zero effect on QCA based devices.

[chrischn82]

okay.
Thanks a lot.

[grassremotecopier]

Hey, for future reference, do you know what specifically caused the brick when you attempted to flash the stock firmware? I might flash back to the stock firmware on my TP-Link Archer A9 v6 to test a few things, and I want to avoid the same problem from occurring for me.

[chrischn82]

I used the correct and newest firmware-file from tp-link-site.
But i used the openwrt-luci firmware webadmin upgrade-tool.

I think i had to read something before. But i didnt read anything.
Special for "downgrading" to manufacturer-firmware you should read something in openwrt.org or github..