Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[dusares]

Hi!

I wanted to upgrade to the latest firmware (2.03NA). Something went wrong and now the router comes up with the orange light flashing. So the system is in emergency firmware upgrade mode. I set my IP to 192.168.0.2 and connect to the web interface at 192.168.0.1. I see a page with "Firmware Upgrade System" and "Version 1.0.0.2". So far so good. I can now select the firmware and click "send". But then nothing really happens. I can wait for a couple of minutes and then run into a timeout. I tried different browsers (Linux: Firefox, Chrome, etc). I even tried it Windows 7 with IE 8 and I get the same result. It seems that the cgi (192.168.0.1./cgi/index) is not really doing anything?!

I tried already the 30/30/30 and some other things I found here in the forum. But nothing works. Each time the system ends up in the same recovery page *but* I can't flash the firmware from here :S

Any ideas?

cu hps

[chascent]

Try this:

put the firmware you want to load into C:\
then
On windows pc get command prompt
make sure you see C:\

connect you PC to a LAN port of the router
from the command prompt type "tftp -i 192.168.1.1 PUT <filename>"

filename is the whole name of the firmware you are loading.
Be patient it will force load the firmware and reboot on its own.

Let me know how you make out

Charlie C

[dusares]

Okay, didn't know you can to tftp with that guy. Will try that later tonight but then in Linux .

Just a quick question. The IP is 192.168.0.1 and not 192.168.1.1?!

[dusares]

Okay, I solved the mystery .

I tried the TFTP method but it didn't work. I checked and the router was not listening to TFTP at all. So I went back and played around with the firmware recovery screen. My problem here is that I run Linux but I have a Windows in a VM. This particular firmware recovery screen needs a machine that natively runs Windows. I tried it in the VM but it didn't work and tonight I had the chance to try it with my wife's laptop and it worked like a charm. Maybe someone should post that in the documentation or FAQ

[Daddicus]

Well, this is a very old thread, but I have the same problem trying to upgrade the firmware on my DIR-825 to version 207. However, your solution doesn't work. I'm running Windows 7 64-bit, so I noted your experience with not working on Linux but it did work on native Windows.

Does anybody know if Windows 7 might have the same issue Dusares had on Linux and solved by going with Windows? If so, how do I get around it?

[FurryNutz]

What FW version is currently loaded?
What HW version is your router?


Is the router work or does it have a problem? It's always not recommended to update FW as sometimes this wont fix other problems that isn't being effected by FW.

[Daddicus]

I have no idea what firmware is loaded, because it doesn't work. Before it toasted itself, it was running 206NA. Hardware version is B1.

I was running the factory 203NA firmware. But, the router took minutes to change pages in the interface. And, I don't mean "a little more than 60 seconds". I mean multiple minutes EVERY time you switched pages. It was so slow at times it would actually time out and require you to log in again (thus, starting over).

There was some indication that a firmware upgrade might fix that problem. And, actually, 205NA did fix it, at least to some extent. But, I was only installing 205 because it was a required step to get to 207, and 207 killed my router.

[FurryNutz]

I would try the Emergency Recovery Mode process and load v2.03 and see if you can get the router to recover and come to ready. If not, then the router needs to be RMAd.

Use IE or FF when you do this.

If it does come back to ready, I would either keep v2.03 if it seems to work well, or if you want v2.07, apply v2.05, then v2.06 before applying v2.07. Don't load any saved configuration files. You need to set up the router from scratch if it comes to ready.

Use the FW Update Process for upgrading.

Let us know how it goes.

[Daddicus]

That link doesn't apply because the page I see when I follow it (or not; doesn't matter) has "Firmware Upgrade System" as a title, not "... recovery ...". However, the screen is VERY similar, and so I tried the same thing with the different buttons. It seems to work, except nothing happens. Sometimes it sits for a very long time (half hour is the most I've had patience enough to wait out), but other times it seems to finish, but there's no change.

I can't believe that with a problem this old and so common that D-Link hasn't figured out the real solution. Once people RMA the things, they have a failing test case. Why haven't they documented how to fix one?

[FurryNutz]

If you can't get the Recovery mode, which you should. I tried it on mine and see the Recovery screen.  I most cases the Recovery mode works one correctly follows the sticky process outlined.

Have you tried using FF to send the firmware? I would also turn off any PC security that you might have running as this can interfere with the data being sent to the router correcty.

If any of these suggestions are not working then it means the router is just beyond any end user resolution and needs to be RMAd and fixed by DLink.

[Daddicus]

I would buy that if I were alone. But dozens of people have reported this exact problem (including the wrongly-named recovery screen) going back over two years.

Someone even showed HTML code that made it work on their router. Unfortunately, that was a different model than mine, so I'm afraid to try it. But the symptoms he corrected were identical (even down to the date displayed on the page).

I suspect the correct workaround is very simple: Create HTML code that mirrors what one would see if the internal code were working, and use that to reapply thought-to-be-working firmware. But, only D-Link would have the knowledge to be able to create such a page.

My problem is that D-Link's 3rd level support is only available 8-4 (my time), which is time when I am at work. Makes it hard to troubleshoot when the only time available is time when I"m not with the hardware.

[Daddicus]

What is "30/30/30"? I've seen that referenced, but can't find a definition for it.

[FurryNutz]

Well you have your options. IF the router isn't working at the moment and if you can try the Recovery mode, then you can't make it any worse. If not, you'll need to find time to contact DLink.

30/30/30 Comes from the DD-WRT site. It how some routers need to be reset during there FW installation. I think some if not most DLink routers don't support this method at all.

Hard Reset (aka 30/30/30 reset):

The following procedure will clear out the NVRAM and set dd-wrt back to default values:
 With the unit powered on, press and hold the reset button on back of unit for 30 seconds
 Without releasing the reset button, unplug the unit and hold reset for another 30 seconds
 Plug the unit back in STILL holding the reset button a final 30 seconds