FS#1082 - TP-link 1043 nd comes into boot loop in 17.01.4

[openwrt-bot]

nkrn:

After flashing 17.01.4 to tl1043nd version 1.8 the device became in boot loop without even coming to SYS led blinking. Trying to get it into recovery mode did not work, I assume it does not start up to that point.

[openwrt-bot]

pepe2k:

Hi @Nektarin,

Could you check if your device contains tftp recovery mode in U-Boot [1]?
If it does, could please upload again 17.01.4 factory image and see if it works?

Do you maybe have (or can make) serial access to your device?

[1] https://wiki.openwrt.org/toh/tp-link/tl-wr1043nd#flashingrecovery_using_tftp_only_without_serial_console

Cheers,
Piotr

[openwrt-bot]

nkrn:

I tried the tftp recovery, as I said the router did not react to pressing the reset button at all. I am going to try the serial access when I get the ttl adapter.

[openwrt-bot]

pepe2k:

Hi @Nektarin,

People sometimes call "failsafe" a "recovery" mode, that's why I got confused and asked about "tftp recovery".

I have just tried 17.01.4 (factory and sysupgrade from 17.01.3) on a v1.8 of this model (with last available vendor firmware: 140319), without any issues.

BusyBox v1.25.1 () built-in shell (ash)

 _________
/        /\      _    ___ ___  ___

/ LE / \ | | | | | |
/ DE / \ | || _|| |) | _|
/_/ LE \ |||/|| lede-project.org
\ \ DE /
\ LE \ / -----------------------------------------------------------
\ DE \ / Reboot (17.01.4, r3560-79f57e422d)
________/ -----------------------------------------------------------

=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.

root@LEDE:/# cat /tmp/sysinfo/board_name
tl-wr1043nd
root@LEDE:/# cat /tmp/sysinfo/model
TP-Link TL-WR1043N/ND v1


Maybe something went wrong during the upgrade. Full bootlog from the serial console should tell you more - please reopen this ticket or issue another one when you get more details.

Cheers,
Piotr