Hi!
I have a DIR 600 B6 model. Before OpenWRT there was 2.18 firmware in it. Yesterday tried to install OpenWRT for the first time, downloaded the image, followed instructions and booted Emergency web interface. The image was successfully uploaded, countdown finished but nothing happened with the router, no reboot, no other lights other then blinking power and port light.
Unplugging doesn't help, it always boots straight to Emergency mode. Tried flashing original firmware back, but stays the same. Is it bricked or what?
Tried it, still the same issue. It uploads the image, then it's seems like nothing is happening. With every image is the same. Tried reseting it and unplugging, but when turned on it just goes straight to Emergency interface. I just don't get it, if it is bricked why is it allowing Emergency interface?
Hi, same issue here. DLink DIR-600 B6/B6E. https://openwrt.org/toh/hwdata/d-link/d-link_dir-600_b6_b6e
Stuck in emergency mode loop.
First time after image pushing leds was blinking for few seconds before behing stable.
Then after that all the times it stuck in emergency mode page. On/off led blinks slowly as when I've pushed reset button for the first time. When uploading an image, the confirmation page shows up, then on/off led and webserver shut down. No blinking as first time that would indicate a memory edition. Only led port indicator is up. When device is re-plugged, it starts itself in emergency mode, with on/off blinking without reset button behing hit.
Tried with in order openwrt-18.06.1-ramips-rt305x-dir-610-a1-squashfs-factory.bin, lede-17.01.4-ramips-rt305x-dir-610-a1-squashfs-factory.bin and lede-17.01.0-r3205-59508e3-ramips-rt305x-dir-610-a1-squashfs-factory.bin image files.
Any help welcome! Sorry for my English.
For me, after opening my device and solder the wire to access the console with an usb/rs232 adaptor (following the "Unbrick" procedure here ). I have my DIR-600b6 back with the stock firmware.
But each time I try to put OpenWrt, it works after fresh reboot, but the very next one it's the same issue ( Emergency Web Interface).
Another thing I have noticed, it seems that if the console is connected while booting, sometimes it causes crash, so disconnect the console after flashing the firmware, and watch the leds.
Finally I've followed instructions in this page, then upgrade to the latest possible version (because of memory limitation of the device) of OpenWrt (19.07.8). And it seems to works ! ! ! Even after multiple reboot and switch off/on. Thanks to this guy.
…lots of grave dinging here, really old devices, really old threads.
Did you check the pages linked in thread, there is an emergeny section. if the „emergency“ room web interface is available on your particular device, then yes (not all 300/600 sub variants have it) https://openwrt.org/toh/d-link/dir-300revb
to be realistic: I would not waste time here anymore and simply donate the device to a recycling station, 32MB Ram hurts, ans some of the devices dont even have sufficient free flash for OpenWRT18 (as not even the small 4MB is fully available for images). And v18 has now accumulated more than 4 years of security issues.
Also note: that emergency web interface additionally has issues for many users nowadays, especially when called from Linux clients, as the recovery web service has improper „http100 continue“ implementation and „modern“ http clients implementations have mostly been changed to require more rigid proper http 10p handling.
Side effect is then: things start to hang.
This is why the older post claim issues with the interface. Windows/Chrome or curl as client can often help.
The emergency interface is working and loads the image, but then restarts into the Emergency-Website.
It's merely used as a bridge for some old consoles and I have the newest OpenWRT on my Main-Router, so security isn't much of a concern there.
Anyway... I don't want to spend too much time on it anyway, so I will likely just throw it away (especially considering the fact that I have 2 more DIR-600).
likely the image does not fit into the flash partition of that device, some boot-relevant code cannot be executed, cannot fully boot to to this.
An OOM could also be the case for 32MB, but flash size is usually the first hard barrier.
happens, when an image is though valid generated, but is too large for the free partition of particular space-limited devices.
There were a lot of dir-600 subvariant, could be that they differ slightly in the available firmware flash partition size, even though all were advertised as having „4MB flash“ and being a „dir-600“
You could try creating a custom built without some components or installing v17 ans using it as 100mbit switch, but then again this is then the case of how much more effort to invest.
The recovery page requires a very old web browser. It is sometimes possible to find the target URL of the "Upload" button in the page source and use curl to directly put the file instead of using a browser.
