OpenWrt Forum Archive

Topic: Recover Bricked DGND3700

The content of this topic has been archived on 22 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi,
I've tried to flash openwrt on my DGND3700, I'm pretty sure because the serial is 2KB..... . So I downloaded openwrt-15.05.1-brcm63xx-smp-DGND3700v1-squashfs-factory.chk and flashed it trough the router firmware upgrade page.
But on the reboot it got stuck on the GLOD (green light of death), the power green light stay one, every other light is off and I'm not able to connect to the router in any way and also the DHCP seems not working.
Have I some way to recover it? Thanks.

If the flashed firmware was bad, the router should enter itself into recovery mode waiting for a firmware via tftp. You can send the firmware with this command (in linux)

tftp 192.168.1.1 -m binary -c put goodfirmware.chk 

Previously to execute this command you need a static IP on your computer (i.e 192.168.1.11).

Othewise you probably will need access via serial console to the device to see what's going on.

h t t ps://kb.netgear.com/22688/How-to-upload-firmware-to-a-NETGEAR-router-using-TFTP

(Last edited by gybrojby on 26 Jan 2018, 15:19)

Ok, it turns out that OpenWrt 15.05.1 has some problem and throws a kernel panic once flashed. This was reported some time ago but not pointed out at the wiki.

OpenWrt 15.05 works ok.

You must use the serial port to unbrick the router.

I updated the wiki with the 15.05.1 issue.

Regards

I cant see a change here: h t t ps://wiki.openwrt.org/toh/netgear/dgnd3700

Why are you using the outdated 15.05? This is the recent firmware version for this device:
Flashing from factory image: h t t ps://downloads.openwrt.org/releases/17.01.4/targets/brcm63xx/smp/lede-17.01.4-brcm63xx-smp-DGND3700v1-squashfs-factory.chk

Flashing from other openwrt image as update: h t t ps://downloads.openwrt.org/releases/17.01.4/targets/brcm63xx/smp/lede-17.01.4-brcm63xx-smp-DGND3700v1-squashfs-sysupgrade.bin

danitool wrote:

Ok, it turns out that OpenWrt 15.05.1 has some problem and throws a kernel panic once flashed. This was reported some time ago but not pointed out at the wiki.

OpenWrt 15.05 works ok.

You must use the serial port to unbrick the router.

I updated the wiki with the 15.05.1 issue.

Regards

Fuck, if I need a serial port then it's a big problem I'm not able nor I've the tools to solder a serial port. I think it is more convinient to throw the router away and buy a new 20 euros TP-LINK  sad


gybrojby wrote:

I cant see a change here: h t t ps://wiki.openwrt.org/toh/netgear/dgnd3700

Why are you using the outdated 15.05? This is the recent firmware version for this device:
Flashing from factory image: h t t ps://downloads.openwrt.org/releases/17.01.4/targets/brcm63xx/smp/lede-17.01.4-brcm63xx-smp-DGND3700v1-squashfs-factory.chk

Flashing from other openwrt image as update: h t t ps://downloads.openwrt.org/releases/17.01.4/targets/brcm63xx/smp/lede-17.01.4-brcm63xx-smp-DGND3700v1-squashfs-sysupgrade.bin

Because of this written in the official page

"Stable releases
If you are a newcomer to OpenWrt, you should install the current stable release. The history page lists all stable releases so far, and the Details Page for your router (check the Table of Hardware) should tell you which image to download and how to install.

The current stable release is Chaos Calmer 15.05.1 released in March 2016.
"

dejawho wrote:

if I need a serial port then it's a big problem I'm not able nor I've the tools to solder a serial port. I think it is more convinient to throw the router away and buy a new 20 euros TP-LINK  sad

Some people reported being able to connect the serial port without soldering anything. The UART adapter costs about  2$.

Since you need to unbrick the board, you only need to send the "tftpd" command to CFE, via the serial port, for sending the firmware via tftp (as I said in my previous message). Even you can omit connecting the RX pin (not comfortable because you won't see what the console returns, but should work aswell). Only connecting GND and TX is enough.

I saw people just using a couple of needles for connecting the serial port. If the contact is not good the recovery just won't work, it won't cause any damage to the board.

Anyway, better to have a pin header properly soldered.

danitool wrote:
dejawho wrote:

if I need a serial port then it's a big problem I'm not able nor I've the tools to solder a serial port. I think it is more convinient to throw the router away and buy a new 20 euros TP-LINK  sad

Some people reported being able to connect the serial port without soldering anything. The UART adapter costs about  2$.

Since you need to unbrick the board, you only need to send the "tftpd" command to CFE, via the serial port, for sending the firmware via tftp (as I said in my previous message). Even you can omit connecting the RX pin (not comfortable because you won't see what the console returns, but should work aswell). Only connecting GND and TX is enough.

I saw people just using a couple of needles for connecting the serial port. If the contact is not good the recovery just won't work, it won't cause any damage to the board.

Anyway, better to have a pin header properly soldered.

So I've bought the serial adapter, soldered the cable, connected everything using putty aaaaand no output from the router.
I've recorded this video showing the solder point and the connection, can you tell me if I've done something wrong:
drive.google.com/file/d/1PPXOGJ8fwxTD3VKYKLuqTMZEyeZqbH2T/view?usp=sharing

EDIT: nvermind, I've reversed TX and RX on the adapter, I connected the router RX with the adapter RX. I was able to flash the new firmware, thanks for the support

(Last edited by dejawho on 30 Jan 2018, 14:58)

Try to swap RX by TX.

The pin markings on the adapter (and router) for TX and RX may have an incorrect reference.

Also be sure you are selecting the correct port on Putty (are you sure is COM3?). Better if you test it with another known working device beforte using it on the DGND3700.

Edit: ok, good to know you finally debricked the device

Regards

(Last edited by danitool on 30 Jan 2018, 15:12)

The discussion might have continued from here.