I can interrupt the bootup when i ping the router on boot up and try to load a firmware up.
At this moment i can get a "CFE>" prompt - but i cant write anything?!?!
I did not do a jtag on mine, I did the serial with the audio jack discussed in this thread but I could never get the boot to stop at the CMD prompt so I followed the above mentioned post to work with the CFE prompt.
Slione thanks for your help but i wont work under Windows XP and hyperterminal. I cant break the bootup and i cant type anything.
I have soldered a new jtag cable and this time it works! So i was able to tjtag it :)
I erased the nvram and the kernel but cant upload a firmware over tftp (it always stops). So i uploaded the original firmware over the jtag cable in roundabout 6 hours. After a reboot i got live signal from the router, he showed me a side at 192.168.1.1 to upload a firmware. So i have uploaded the original firmware again but this time over the http interface and after another reboot the router works fine - yippie!
I have soldered a new jtag cable and this time it works! So i was able to tjtag it :)
I erased the nvram and the kernel but cant upload a firmware over tftp (it always stops). So i uploaded the original firmware over the jtag cable in roundabout 6 hours. After a reboot i got live signal from the router, he showed me a side at 192.168.1.1 to upload a firmware. So i have uploaded the original firmware again but this time over the http interface and after another reboot the router works fine - yippie!
Glad to hear that you got it working! _________________ WRT1900AC v1-build r30731
Posted: Tue Jun 23, 2009 19:38 Post subject: tftp recovery
I seem to have bricked one of my WRT610N as well.
Since we now have DD-WRT builds which are smaller than 4MB, I kind of assumed that it should be possible to recover just using the CFE TFTP server, but this somehow doesn't work. I can tftp a file to the device, and the transfer succeeds
Code:
tftp> put dd-wrt.v24-12367_mini_usb_ftp_wrt610n.bin
Sent 3437568 bytes in 6.2 seconds
but the device will just go into the reboot loop afterwards anyway. 30/30/30 before and after a flash haven't helped. I've tried this with a variety of DD-WRT images, both new and old. Anything bigger than 3.8MB of course won't work, since the transfer fails.
Anyone got a good tip (before I set out to get the hardware for a serial port)?
I've also made sure to get the "sweet spot" where the device will actually stop answering pings after the TFTP upload to indicate that it's writing flash. It never finishes with that here, though (waited 20 minutes)
Posted: Thu Jun 25, 2009 20:08 Post subject: I have the same issue -- Did you solve it?
owagner wrote:
Yes. Also tried tftp2 on Windows.
I've also made sure to get the "sweet spot" where the device will actually stop answering pings after the TFTP upload to indicate that it's writing flash. It never finishes with that here, though (waited 20 minutes)
Is tftp'ing a mini build known to work?
Best Regards,
Olli
Did you solve this? I just did the same and mine is in a reboot loop also.
Now got serial console attached, read-only (I don't want to void the warranty so obviously just yet). This is what I can see from the CFE tftp process:
I now managed to debrick the device using the aforementioned instructions originally from reames (thanks!), but without opening the WRT610N.
The serial port is actually available from the outside -- if you look carefully into the "Internet" ethernet jack, you can see 4 pads labeled GND, 3.3V, TX and RX on the PCB. There is probably some proper plug for this available to Linksys technicians.
Since I didn't have a DKU-5 cable nor a stash of MAX323s, I took an old WRT54GS, soldered two cables to it's second serial port (the device is easy to open and there are plenty of instructions for doing so on the net) and used this as a console gateway (actually using "remserial" to get the port onto my main linux box, since I didn't find minicom or similiar for dd-wrt)
I then simply held those two cable ends against the RX and TX pads in the WRT610N jack and pasted the load and flash commands into the terminal. GND connection was established using a crocodile clamp cable connected to the USB shielding frame on the WRT610N and the ethernet plugs shielding frames on the WRT54GS.
After literally 50 or so attempts -- it's really, really hard to hold the cables steady enough for the serial console to work properly -- I finally got them through, tftp'ed the original firmware and the WRT610N came up with a "Management Mode Firmware Update" web GUI, where I could then again flash the original firmware.
Incidentally, I'm still interested to know why TFTPing a <4GB DD-WRT image didn't work for me.
Joined: 31 Aug 2008 Posts: 27 Location: Toronto, Canada
Posted: Sun Jun 28, 2009 19:21 Post subject:
belmarduk wrote:
Okay, I got a DKU-5 cable and connected it to the router as per documentation on this thread.
The problem is when the terminal is connected, I only see garbled text "YYYYYYYyyyyyy" on the terminal.
I don't know why. Anyone could shed some light over here?
I reversed the RX and TX cable and I can English text, mixed with random characters. Since I do not have Hyperterminal I am using Termite 2.3. I am not sure if this has to do with my issue!???
Joined: 31 Aug 2008 Posts: 27 Location: Toronto, Canada
Posted: Sun Jun 28, 2009 21:56 Post subject:
belmarduk wrote:
belmarduk wrote:
Okay, I got a DKU-5 cable and connected it to the router as per documentation on this thread.
The problem is when the terminal is connected, I only see garbled text "YYYYYYYyyyyyy" on the terminal.
I don't know why. Anyone could shed some light over here?
I reversed the RX and TX cable and I can English text, mixed with random characters. Since I do not have Hyperterminal I am using Termite 2.3. I am not sure if this has to do with my issue!???
(0xBC04001C)
Glad to hear you got it! It is quite an adventure. 