Posted: Mon Apr 23, 2012 4:57 Post subject: wrt54g v5 Question about freeze.
Thanks in advanced for taking the time to read my post; I’ll try to explain the best i can.
I own a wrt54g v5 router that was given to me with the DD-WRT v24-sp2 firmware version, but now i think i know why my friend gave it away to me, after a while of working, it freezes, by freeze i mean no longer have internet access, unable to ping the router IP (192.168.1.1), the only why the router works again is unplugging the power cord and plug it again.
After a lot of reading the forums, other websites and wikis, I know that this version of router (v5) has some limitations with the hardware (memory), in fact i followed instructions given here:
It said Success but after rebooting the router just won’t work, it starts by blinking the power led, after that, every other led blinks and start over doing the same thing, even turning it off and on again.
After that I kept reading how to solve that problem and found out that by doing a hard reset or 30/30/30 reset I could get the router into a management mode making it possible to upload a new firmware.
I reuploaded the micro DD-WRT v24-sp2 recommended in official dd-wrt website for my router version, the router works again, but I have the same problem, freezing frequently...
How can I install the original firmware back? is there another method? Is it possible that this router has a CFE not compatible with original firmware anymore?
Any help would be very much apreciated.
Router model: WRT54G v5
Actual firmware: dd-wrt v24-sp2 micro
Problem: Freezing, unable to ping after that, only works again after power cycling.
Lastest original firmware (From offical website: FW_WRT54Gv5v6_1.02.8.001_US_20091005.bin
sounds like a hardware failure. corrupted RAM or flash maybe. just try stock firmware again. or invest few dollars for a newer unit. _________________ RT-N66U @ KingKong Build 21395M 64k / BS Build 21570
TL-WR1043ND @ BS-build 19519 WDS AP
TL-WR841ND @ BS-build 18777 WDS Client
sounds like a hardware failure. corrupted RAM or flash maybe. just try stock firmware again. or invest few dollars for a newer unit.
I've tried using original firmware using the method described in the link above with no luck, the router wont boot, it never stop restarting and all leds going on and off, I put dd-wrt micro back and works again but keep freezing.
A new unit would be great but here in my country the cheapest model a generic one (not good brands) is over 90$...That is 15% of my monthly income.
If it is a corrupted ram or flash? Is there a way to repair it somehow?
I put dd-wrt micro back and works again but keep freezing.
You would not be able to simply flash micro back on if you had reverted properly.
For common problems with dd-wrt installation, see the peacock announcement. If you still need assistance, make sure you provide ALL the information that is requested in the peacock announcement. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor. So See this:
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
This time I used the Manual reversion (MAC address and serial # restored), tried to upload in management mode 2 versions of original fimware, first the latest provided by linksys FW_WRT54Gv5v6_1.02.8.001_US_20091005.bin, after several reboots and lights going on and off it came back to life.
I was able to access the web gui, but again, after 3 or 4 minutes conected, it starts rebooting non stop, after 5 or 6 reboots it come back to normal again.
Any ideas? Should I stop wasting time on this router?
Last edited by retghy on Tue Apr 24, 2012 20:51; edited 1 time in total
yes you can do everything via telnet. what i used o do is whenever i needed the web gui(rarely), i went into telnet and typed httpd. when i was done with the web gui, i typed "killall httpd". A pain in the ass but it worked for me.