OpenWrt Forum Archive

Topic: TP-Link TL-WR1043ND FailSafe mode

The content of this topic has been archived on 19 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi,

- TL-WR1043ND briked
- can ping 192.168.1.1

Tried getting into failsafe mode but did not succeed asdescribed here:
http://wiki.openwrt.org/toh/tp-link/tl- … lsafe.mode

Tried at boot sequence immediately after the SYS turns on with QSS pressed for long time, or multiple times.
Tried even with reset pressed multiple times (when reset holds then it restores to factory mode).
Unfortunately the factory mode does not reset all the configuration on the router so Luci is still displaying an error page with user or password incorrect even though it did not asked for it previously so when I go to http://192.168.1.1 it redirects to the error page instantly.

Is there any other known way to get into failsafe mode with this hardware?

Thanks in advance!

telnet works?

nebbia88 wrote:

telnet works?

no ssh
no telnet
only ping

did you get the FAST sys led flashing after pressing random buttons many times during first seconds after poweron?

nebbia88 wrote:

did you get the FAST sys led flashing after pressing random buttons many times during first seconds after poweron?

Nope, that was my problem.

Although I solved it, seems that it was flashed with a wrong verison and Chrome & Firefox cached the "wrong user/pass" fail page thus displaying it whenever I tried to access 192.168.1.1. When tried with IE which did not cache any of this information I found myself in the login screen of some original TP-LINK firmware.
I think that is why I was not able to boot into failsafe mode, since OpenWRT was not installed. it was overridden with a factory version.
Managed to update it to latest TP-LINK.

Maybe I will give it a shot for some other time, the nerves were enough for this time smile

.... I really cannot image how is possible to flash the tplink firmware wihout knowing  it -.-

I think the documentation is dead-wrong.

You must press the Button of the OpenWrt-Device only ONCE. But you must press it at the right moment.

The (new?) tcpdump-feature enables you get a visual on when this moment arrives. Usually it is a time widow, a couple of seconds after connecting the device to the power and also, it last only a couple of seconds, to keep boot-delay low. I think 2 seconds are frequently used.

Do as the wiki says, but
___REPEATEDLY___ press the QSS-Button untill you see one of the LEDs (the sys?-LED) blinking very fast
now: telnet 192.168.1.1

I've done this procedure 7time the day before yesterday. It worked every time very reliable without employing tcpdump.

I think the wiki is (again) wrong, when it says you need to KEEP THE BUTTON PRESSED. You rather need to PRESS THE BUTTON REPEATEDLY.
There seem to be some idiot/troll that keeps writing bullshit-information into the wiki.

The discussion might have continued from here.