Joined: 06 Jun 2006 Posts: 37 Location: Montreal, Canada
Posted: Fri Jan 16, 2009 2:25 Post subject: WRT54G 1.0 very close to unbrick, missing small input
I am trying to unbrick my v1.0, bricked with v23 sp1 DD-WRT years ago.
I have searched the web and here and usually there is a tutorial on how to short pin 16, but never found that tutorial for v1.0, always v1.1+. Chips are totally different on v1.0, even the antenna is totally different.
The power LED flashes very fast and after about 20 seconds it lights permanently, but the DMZ LED did not light up. In this case Bootloader and Kernel (firmware) are intact, only a wrong configuration from locked up the router. This can happen if a wrong or corrupt value exists in the NVRAM. Here simply clearing the NVRAM should solve the problem.
Except my power LED NEVER flashes (always on) and I have a red DIAG led which flashes 13sec and then stays on rock solid, like the power led. The DMZ led always stays off.
First, does this mean it's bricked differently than stated above in #3?
Second, the small input I need:
I do get 3 to 5 ping responses when I power up the router, but it's erratic, sometimes I get 3, sometimes 4, 2, 5, 1 or none at all. Sometimes I get 2, a timeout and another ping and then timeouts. The ms increases from the 1st to last ping. Telnet is not working, cannot on port 23, it says.
I have tried to TFTP v24_mini_std while I plug the router using command prompt tftp and linksys tftp.exe utility. I have tried over 30-35 times differently and it always timeouts the same way.
Do I have a really really really bad timing issue here or is it possible the router just doesn't want to accept my tftp?
tnx! _________________ Frank
Buffalo WHR-G54S v24-sp1
WRT54G2 v24 sp1
WRT54G v5 v24 sp1
Weird WRT54G v1.0 not working
Linux openSUSE 10.3 KDE 64-bits
Could there be a firewall preventing you from TFTPing? (Have you ever successfully done it before?)
If that's not the case, then the only way to recover would be to use JTAG. Pin shorting is never recommended, and can cause permanent damage to the flash chip. If it is indeed an nvram problem, then it wouldn't get you anywhere anyway.
Use JTAG to clear the nvram, and it should work. If not, clear both nvram and kernel, then TFTP a new image. _________________ WRT54G v3 - v24 r14471M NEWD Eko - AP
WRT600N v1.1 - halfway there!
Se7en is Darker...