Posted: Tue Aug 17, 2021 12:02 Post subject: Possibly bricked my Linksys WRH54G
Hi guys,
I am new to flashing firmware over devices and I think I may have bricked my Linksys WRH54G router. I had one of those just lying around and recently found out that you can upgrade to the dd-wrt firmware to give it a Repeater functionality. Anyhow, I followed the instructions on https://wiki.dd-wrt.com/wiki/index.php/Linksys_WRH54G but was confused on which firmware to upgrade it to (this link has two micro builds and when I searched it on the router database at https://dd-wrt.com/support/router-database/?model=WRH54G_?, there was another build, also I am not sure if these three builds are actually the same or not). I picked the firmware I found on the router database but ever since the upgrade finished I have been unable to ping to the router nor can I access the router webpage. Usually I get the "Request timed out." message with the occasional "Reply from 192.168.1.100: Destination host unreachable." but sometimes when I unplug the router, re-plug it and immediately ping it I get a response with ttl=100. From the Peacock Thread I have learned that this message means that the router requires a firmware immediately. However, I have been unsuccessful in producing this message consistently. I have tried the 30 second reboot, the 30/30/30 reset and just normally turning it on and off, and now I do not know where I am at anymore. Currently, I get the power and Ethernet connection lights (hasn't changed since the upgrade or even before that). I think the next thing to do would be to recover with TFTP or JTag. I was just wondering if I could receive some guidance on what to do next, how to confirm that my router is 100% bricked since that ttl=100 response is making me unsure, and what could I have done wrong (incorrect firmware, possibly defective Ethernet cable, etc.) so that I don't do it again. I am pretty sure the power supply is correct as the router was working properly before I attempted this upgrade. Also, I wasn't sure what the Peacock Thread meant by, "Make sure that you set the IP on your computer to the same first three octets of the IP you are trying to ping." (Note 6, paragraph 10) as what I understood was that the IP address is specific to a connection, not the computer as a whole. Any help is appreciated!
You are trying to access your router via http://192.168.1.1, correct? Your PC's IP address is set to something like 192.168.1.2 (or .5, .10... something other than .1 or .255), correct?
Yes, I am trying to access the router via http://192.168.1.1. When I go into the ethernet properties, it shows that my IPv4 address is 192.168.1.100 and my IPv4 DNS Servers are 192.168.1.1. From surfing online, I think this is how one is supposed to find out their PC's IP address, correct?
I would suggest having a serial USB-UART-TTL adapter connected with serial console up in PuTTY so you can see what is breaking, if anything.
Yes, I am sure my browser is trying to access http://192.168.1.1. I am unsure what you mean by booting up with TTL=64? I just do "ping -t 192.168.1.1" in the command prompt and get Server Timed Out responses.
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Tue Aug 17, 2021 16:34 Post subject:
What I mean is, when you power on the router, with ping -t 192.168.1.1, do the responses go from destination unreachable to TTL=100 to unreachable to TTL=64. Referencing the Peacock thread, if it only responds with TTL=100 and not a TTL=64 response, then it is bricked and requires a TFTP flash back to stock or trailed build. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
What I mean is, when you power on the router, with ping -t 192.168.1.1, do the responses go from destination unreachable to TTL=100 to unreachable to TTL=64. Referencing the Peacock thread, if it only responds with TTL=100 and not a TTL=64 response, then it is bricked and requires a TFTP flash back to stock or trailed build.
Ah, okay. The responses are "Request Timed out." with a "Destination host unreachable." every now and then. I get a TTL=100 only rarely when I ping it as soon as I plug the router in.
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Wed Aug 18, 2021 2:48 Post subject:
Ping, power, put or ping, put, power. You should be able to use the Linksys utility if you are on Windows, otherwise read the wikis that I have already linked.
Ping, power, put or ping, put, power. You should be able to use the Linksys utility if you are on Windows, otherwise read the wikis that I have already linked.
When you are using a TFTP client, the command or button to push the firmware image to the router is "put". Read the wikis...
Hi, sorry I got bogged down with something else. The wikis and articles you provided were super helpful. I managed to un-brick my router and flash 14929 via TFTP2. Just for future references, I changed my ping command to "ping -t -w 1 192.168.1.1" which shortened the intervals between each ping and helped me catch that small window when I would get a TTL=100 reply from the router. I was wondering if you could provide any insight as to why my router got bricked the first time so that I don't end up making the same mistake as I still intend on configuring it as a repeater.
