[SOLVED] How do I revert WRT54GL back to Linksys stock firmware

Hello everybody,

I'm new here and need your help. Pls. have patience since I'm not a native speaker.
I like to revert my WRT54GL back to the original firmware but the LuCI interface complains about wrong format.
Where do I find a step by step guide for my goal?

Heinz (from Vienna, Austria)

Just buy new hardware it's not worth your time to support such ancient stuff.


I agree.

I cannot speak from experience. As, out of all the original Linksys WRT-series routers I've owned, I've never reverted back to stock. Also please be advised that the original firmware is vulnerable due to its age and therefore, unpatched state.

Also in case it's not clear this is a placeholder, you need to find the appropriate url on Linksys site for your particular version.

1 Like

Thanks to dlakelan and lleachii.
Agreed it's an old device and might be unsafe with Linksys`latest firmware (which is from 2016 BTW). It was not in use lately but I wanted to have it ready as a spare in case of a breakdown during a weekend when shops are closed.

Your suggestion didn't work. I had to cut off the first 32 Bytes and create a trx-file. The trx was usable with the LuCI GUI. Now I back to Linksys stock firmware.

Last question: How do I mark this thread "solved"?

Regards, Heinz

1 Like

If your problem is solved, feel free to mark the relevant post as the solution (like in the example below); and edit the title to add "[SOLVED]" to the beginning (click the pencil behind the topic).


(Also, no need to sign your posts.)

The length of time an unmaintained Linksys firmware from 2016 can remain connected to the internet before compromise might be measured in minutes to hours. I regularly receive probes on my router which I limit the rate of with advanced firewall techniques. If you want a good backup device may I suggest one of the inexpensive openwrt supported travel routers, perhaps from gl-inet


Hello lleachii,

I'm old, born during 2nd WorldWar. We were educated to be polite, greet people, sign, ... So I stick with this behaviour.

Regards, Heinz

Hello dlakelan,

suggestions are always welcome. I'e never heard of GL-iNet. Do you know if those routers are sold in local shop in Austria. I prefer to buy from a local dealer, so they can survive. First supermarkets and now online shops killed small retailers within short distance from home. When you get old and can drive any more you are thankful for dealers within reasonable walking distance or reachable by public transport.

Regards, Heinz

I don't know if they have local shops, as they sell direct and through Amazon, at least here in the US. They have what seem to be well-supported, good quality, single-band units with reasonable flash and RAM for US$20 or less.


I just broke down to temptation and purchased one of their tiny, dual-band travel routers and am very impressed. Now, since I already have too many routers, to figure out what to do with it :wink:

How do you check for these "probes"? I'm running latest OpenWRT but I'm just curious. Thanks.

I log the packets to the kernel log. So I see things like:

Dec 11 21:14:36 pico kernel: [362972.633568] INPUT DROP: IN=veth1 OUT= MAC=xxxxxxxx SRC= DST=xxxxx LEN=40 TOS=0x00 PREC=0x60 TTL=238 ID=54321 PROTO=TCP SPT=34170 DPT=1503 WINDOW=65535 RES=0x00 SYN URGP=0 
Dec 11 21:15:13 pico kernel: [363009.060896] INPUT DROP: IN=veth1 OUT= MAC=xxxxxxx SRC= DST=xxxxxxxx LEN=40 TOS=0x00 PREC=0x60 TTL=234 ID=45670 PROTO=TCP SPT=51238 DPT=3393 WINDOW=1024 RES=0x00 SYN URGP=0 
Dec 11 21:15:20 pico kernel: [363015.848102] INPUT DROP: IN=veth1 OUT= MAC=xxxxxxxxx SRC= DST=xxxxxxx LEN=40 TOS=0x00 PREC=0x60 TTL=242 ID=54321 PROTO=TCP SPT=34232 DPT=443 WINDOW=65535 RES=0x00 SYN URGP=0 

As you can see, I get some kind of probe every few seconds :wink:

But my router is running Debian, only my APs are running OpenWrt. Still it should be possible to do logging in OpenWrt firewall, you could add an input rule with "extra arguments" for logging. If you do this though you should probably set up a more robust logging system and either log to a USB drive or a remote machine.

Thank you for pointing me to the Guidelines. I hope I will not forget to let my post here unsigned, might forget since I sign post on all other Forums.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.