Print

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

[enphor]

After the FW update, it just hung and sat there with the orange blinking power light. I tried the reset proceedure and do get to the recovery firmware screen.

The problem is that I consistently get an "incorrect hardware ID" on every firmware for the DIR-655 that I try to use. Even older ones that I knew worked since I had previously used them to upgrade.

This is over a wired connection, the DIR-655 is H/W Ver. B1, F/W Ver: 2.00NA on the label. I even tried loading the 2.00NA firmware and get the same error.

Any help is appreciated!

[FurryNutz]

If the recovery mode failed, then youll need to phone contact DLink support and get this unit into RMA.

[coxhaus]

Try using the check for new software button on the router to download the 2.10NA firmware. Then upgrade using this download. It worked for me. I have hardware Rev B1.

PS.
I am asumming you can recover to the old version.

[FurryNutz]

Thats the thing, he can't get the router to come to ready at all thus no access to the routers web page.

[enphor]

Yup, can't get to the router's screen , only the emergency firmware boot loader.

Guess I will contact Dlink for an RMA. Very unfortunate

[coxhaus]

Is there a way to tftp a firmware to the router to get it up running? I have done that in the Cisco world.

[FurryNutz]

Nope.

[enphor]

Just got off the phone with D-Link support. Went through the same procedures that I have already tried. I was then told that I'm out of luck since the router is out of warranty.

The route was working perfectly until I upgraded the FW to 2.10NA. I did this b/c it said it had better support for iOS6.

So in the end the firmware process got botched, there is no way to recover from it, and D-Link support told me that I have to "buy another router".

In the end, I will be buying another router, but it will not be another D-Link.

I hope this serves as a warning to anyone with an out of warranty router... that upgrading the FW is a tremendous risk of loosing your investment.

[FurryNutz]

Sorry that they didn't RMA it for you.

I would recommend that next time you want to upgrade FW, please visit the Mfr community forums before upgrading. I believe that help, advice, asking questions and getting official FW upgrading process information first off before attempting any FW upgrade, will help you avoid problems like this. FW updates do work if done properly and v2.10NA does work when applied correctly. Also people need to understand that it's always not necessary to update FW all the time or have the latest and greatest. FW updates usually don't fix the many problems seen here in the forums.

Good Luck with your endeavors.

[enphor]

Sorry that they didn't RMA it for you.

I would recommend that next time you want to upgrade FW, please visit the Mfr community forums before upgrading. I believe that help, advice, asking questions and getting official FW upgrading process information first off before attempting any FW upgrade, will help you avoid problems like this. FW updates do work if done properly and v2.10NA does work when applied correctly. Also people need to understand that it's always not necessary to update FW all the time or have the latest and greatest. FW updates usually don't fix the many problems seen here in the forums.

Good Luck with your endeavors.

So you are implying that in incorrectly applied the firmware update and caused this myself?

If there is any chance of a brick if you don't follow specific details, that's pretty serious and it should be posted in big bold letters on the D-Link firmware download page. The answer of "go checking on support forums" for the "official FW upgrading process" is not an acceptable procedure for going through a standard FW upgrade.

I did this FW for the iOS6 benefits, it was not a frivolous upgrade for fun.

What irks me is that I can get to the emergency bootloader where I can upload a firmware package to. But unfortunately I get an "incorrect hardware ID" error on every FW package that I try. I was hoping DLink support would have a FW package .bin that would force the re-flash. I specifically asked that and the woman put me on hold, then came back and told me "sorry we don't". The fact that this emergency bootloader page exists is specifically for these situations, as a fail-safe recovery option, and its lack of use demonstrates to me that D-Link hasn't bothered to care about their customers to allow them to be able to get back to a working condition with it.

[FurryNutz]

What browser was used to manage the router and get to the Emergency Recovery page?
What OS are you using to connect to the router?

Not implying that you did any thing wrong. Just pointing out that most users presume that just updating FW regardless of benefits or not, is always not necessary and seems to cause more problems than fixing.

[enphor]

I used FF to perform the FW update. After it bricked with the yellow flashing power light. I used FF to get back to the router on the default 192.168.0.1 IP. It would not allow me to upload a new FW package to the emergency bootloader. The router would then just lock up and the power light would turn solid.

After power cycle, I then tried Chrome to see if it was different. That allowed the FW upload, but then would give me the "incorrect HW ID" error.

I hear you on the FW updates not being needed all the time. And I also hear you that it can cause problems, as I'm a perfect example of that!

[FurryNutz]

Does IE 8 or 9 with compatibility mode work?
Did you download the v2.00 shipping version?

I remember someone said that using XP with IE v6 worked best. Don't remember where I saw that though.

Ya seems like it's almost there.

[enphor]

Hey its worth a shot. I'll try messing with different browsers. Yup I did try the shipping v2 version. Interesting if it is a browser thing. Maybe the emergency bootloader is a bit behind the times when it comes to browsers. It does have a date of 2009 on it.

[FurryNutz]

I also remembered, turn OFF any and all 3rd Party Anti-Virus and Firewalls to be sure. You don't want any thing to interfere. Keep us posted. Hope this might help.