Print

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

[MontrealPaul]

Haven't found the time to deal with Tech Support, yet, and as I really need to fix this situation soon, I've ordered a refurbished DIR-845L from BB ($39.95 CDN!)
Still pissed at D-Link that their FW would brick their hardware, but willing to give them one more chance...

[FurryNutz]

Post here if you need any help with the 845:
http://forums.dlink.com/index.php?board=394.0

Please try the router out first before updating any FW.

Haven't found the time to deal with Tech Support, yet, and as I really need to fix this situation soon, I've ordered a refurbished DIR-845L from BB ($39.95 CDN!)
Still pissed at D-Link that their FW would brick their hardware, but willing to give them one more chance...

[MontrealPaul]

Youbet! I've learned my lesson (although I thought that 2.11 was supposed to be stable, having been out for quite some time, and would resolve some issues).
Thanks for the link - I'll add it to my "config" folder.
Cheers!

[FurryNutz]

v2.11 FW is stable. Just application process needs to be followed for all future reference! 

See you on the other thread.

[Jughead135]

Sorry to have dropped off.  Paul, I got your PM (belatedly, spam filtered)--thanks for the reminder.

After what seemed like a promising start with the tech supt guys that Furry hooked me up with, I hit the wall.  While they provided a RMA, it turned out it was contingent upon a current/active warranty--which, as I stated earlier, is not the case for me.

Since I'd already bought a new router (not worth the aggravation for a sub-$100 gizmo), I just let it die there--and forgot to come back here to follow-up (my bad).

Thanks to all for the help (particularly Fuzzy).  Sorry my story doesn't end better....

[FurryNutz]

Sorry you couldn't get the 655 working or replaced.

Hope the new router works well.

Good luck.

Sorry to have dropped off.  Paul, I got your PM (belatedly, spam filtered)--thanks for the reminder.

After what seemed like a promising start with the tech supt guys that Furry hooked me up with, I hit the wall.  While they provided a RMA, it turned out it was contingent upon a current/active warranty--which, as I stated earlier, is not the case for me.

Since I'd already bought a new router (not worth the aggravation for a sub-$100 gizmo), I just let it die there--and forgot to come back here to follow-up (my bad).

Thanks to all for the help (particularly Fuzzy).  Sorry my story doesn't end better....

[MontrealPaul]

Thanks for the response, Jughead! Sorry you didn't any satisfaction from D-Link either...
Like you, because it's no longer an urgent issue, I still haven't gotten around to contacting D-Link "support" to try to revive my bricked DIR-655 (and your experience shows that the "best" they can do is offer an RMA, but... oh, dear, out of warranty, so so sorry, S.O.L.)...
Nevertheless, my OCD hates to see this thing "almost" ready, booting with the web interface but not accepting a "valid" FW image, so I'm still going to try... one day...

[hindianspring]

This fixed my toasted 655 B1 . Went thru the same pain last night. Downloaded from Canada site (http://support.dlink.ca/FAQView.aspx?f=sY5vcvfAuAV6bXgi%2f8WoVw%3d%3d#655a) and UK (http://www.dlink.com/uk/en/support/product/dir-655-wireless-n-gigabit-router?revision=deu_revb#downloads) and believed it was toast. Tried this morning and noticed it working Hardware Version: B1 Firmware Version: 2.11NA. Hope this helps  .

[FurryNutz]

Link>Welcome!

• What region are you located?

Be sure to follow this for loading future FW updates:
 FW Update Process

This fixed my toasted 655 B1 . Went thru the same pain last night. Downloaded from Canada site (http://support.dlink.ca/FAQView.aspx?f=sY5vcvfAuAV6bXgi%2f8WoVw%3d%3d#655a) and UK (http://www.dlink.com/uk/en/support/product/dir-655-wireless-n-gigabit-router?revision=deu_revb#downloads) and believed it was toast. Tried this morning and noticed it working Hardware Version: B1 Firmware Version: 2.11NA. Hope this helps  .

[Jughead135]

Necropost warning....

So, digging around in a box of old routers (setting up a switch/access point as an extender, looking for an appropriate one to try), I put my hands on the DIR-655 and couldn't understand why it wasn't working.  I vaguely recalled having a bricked router, but I'd forgotten all the troubleshooting.   I re-invented the wheel, until my search found my own posts on this thread from almost 10 years ago....

This router is pretty old, this is obviously only a playing-around hobbyist type issue at this point--but, I wonder, was this ever solved??  I'm exactly where I was at the time of the previous posts:  the router will show me the emergency recovery page, but it will either ignore all attempts to send it an image, or respond with "incorrect hardware ID image."

The only thing I tried that I did not do before was tftp--which 100% comes back with "connection attempt failed"....

So...  anyone ever end up getting a bricked DIR-655 resurrected? 

[davevt31]

Emergency Recovery:

http://forums.dlink.com/index.php?topic=44909.0

Try with an older version of the firmware if the newest one is not working.

Here is link to FTP site, just pick your Revision version and many of the older firmwares are there:

http://legacyfiles.us.dlink.com/DIR-655/

[Jughead135]

Emergency Recovery:

http://forums.dlink.com/index.php?topic=44909.0

Try with an older version of the firmware if the newest one is not working.

Here is link to FTP site, just pick your Revision version and many of the older firmwares are there:

http://legacyfiles.us.dlink.com/DIR-655/

I've tried ALL of that (both during my original go-'round 10 years ago, and now again before I found my own posts on the subject).  The issue is that the router appears to ignore any attempt to send the .bin file (though, it occasionally responds with the "wrong hardware" error).  This is true of multiple browsers, multiple PCs, multiple connection sources, and every Rev posted on the FTP site.

[davevt31]

Probably dead then, too bad it was a good router (I had one too) back in the day.