You can try the TFTP deal when booting.
Grab a Network Hub.
Plug it into computer and set a static TCP/IP address to the computer as 192.168.1.10, default gateway 192.168.1.1, and 255.255.255.0.
Using the hub you don't have to wait on router bootup to get an IP address.
Then plug your router into the hub.
Start ping 192.168.1.1 and plug in your router. Watch and see if you get any replies at all. If you do you can try TFTP as soon as you get a ping reply. You may have to try it a few times to catch the right time.
If you get no pings, this way, then get the solder gun. :)
Categories: Troubleshooting
Well, my WGR614L died yesterday and I *think* it's my own fault. I had loaded the most recent build of DD-WRT that I know of, which I believe is this one:
http://www.myopenrouter.com/download/12568/DD-WRT-build-svn-revision-12357M/
Out of nowhere, it just died, stuck as in the photo shown. The "Test" LED is constantly lit. When network devices are connected, they show as connected, but no wireless access.
A 30-30-30 reset didn't have any effect, unfortunately. I haven't yet tried to debrick it yet, since I don't have a soldering iron handy to connect the TTL cable, but will do that soon (I really need to get my own soldering iron!)
Does anyone have any magic tricks or insight as to what might have happened? I unfortunately did not follow the good advice of the DD-WRT forums by performing a 30-30-30 before and after flashing, so maybe that contributed to the sudden failure.
Peter Redmer
Administrator
Blog | Twitter | Google Buzz
svn12357 is very, very old, out of the days where things changed a lot and when there were instructions like:
For upgrade when already running dd-wrt (IMPORTANT!!!):
- if your dd-wrt build is less then 11600 please
use dd-wrt.v24-12030_WGR614v8-L_mini.bin file. Then
you can upgrade to any build listed below.
- if your dd-wrt build number is greater then 11600,
you can upgrade directly using any build listed below.
Older builds than 11600 had not enough free memory to flash standard builds without flashing to a mini build of the same number first. So 12357M might be o.k. if you follow these instructions.
Actual build is 13577.
I also tried to upgrade to build 13577 (big)
30-30-30 OK
Flash OK
Reboot (automatic) OK
And then it informed/asked (?) about netadresses (?) and wlan (?) ( my memory about it = ?)
and I had the choise between "Continue" or "Quit"
I choosed "Continue"
After that my WNR3500L were froozen and act exactly as your.
Could it be some serious bug for Netgear routers in that build ?
After that there were normaly no respond on ping.
If I used tftf2 according to instructions I had 1-2 ttl=100 respons, but no upgrade
If I pushed Reset and powered up and after connection established I released Reset button I get 3-4 ttl=100. But no luck with tftp2 and upgrade.
After xxx attemts in different ways the router is now completely dead. No ttl=100 respons in any way.
So it looks like some soldering.
But I really don't like the 13577 release
Have succesfully upgraded my WGR614L to ed4c0786fdb73e222618235d86655dac ./dd-wrt.v24-13577_NEWD_std-nokaid.bin from svn13064.
I know we are getting a little off topic here but for my WGR614L I just use what is recommended from DD-WRT using their database.
http://dd-wrt.com/site/support/router-database
Right now it recommends 13064 and it seems to work fine for me and apparently for you to Schugy.
ive got the same problem with my v8. i had dd wrt running on it for about 2 years and when i tried to upgrade the firmware it froze half way through and it is now bricked. i can get a constant ping with TTL 100 though. ive tried a couple tftp utilities specifically for routers but no luck. i dont have a hub to try it with either. ive also made a jtag cable but ive searched and searched with no success on finding the specifics on how to load firmware. i dont have much experience with tftp. and next to none with a jtag. any help would be much appreciated.
Thanks, Taylor
Tathagata Das said: Do you have serial cable set up ?
no i havent purchased a serial cable.
Can you get to it via telnet, SSH or anything? If not and you can't catch it fast enough to tftp a file onto it you should get the serial cable.
BrandonC said: Can you get to it via telnet, SSH or anything? If not and you can't catch it fast enough to tftp a file onto it you should get the serial cable.ive tried telnet and haven't got it to catch, i read that using a hub will work because it doesnt wait for windows to recognise the connection. ill try the hub first because i can borrow one, but if that fails it looks like im gonna have to buy the serial cable. thanks for the advice Brandon.


RSS
