OpenWrt Forum Archive

Topic: Trendnet TEW-691GR is not accessible after first flash

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

Good time of a day!
I have initiated flashing my TRENDnet TEW-691GR with
https://downloads.openwrt.org/barrier_b … actory.bin
and went walking... When I came home, it was not accessible!
When it boots, the WPS led is blinking (like it is booting), then it becomes always on. But it does not answer:
1. Tried to set my comp to "DHCP client" - no answer
2. Tried to set static IP with different masks and addresses on my comp (192.168.0.2 - 192.168.10.2) - no answer
3. It enters Failsafe mode!!! but only by led indication (after rebooting and pressing hard button, the WPS led begins blinking very fast until next reboot). With different IPs on my computer I get:
a. no message on my udp sniffer from boot
b. no connection through Putty and Windows Telnet

When I connect something to LAN(1-4) or WAN port, it's led is working, but it seems that the router doesn't see it's RJ45 ports :-)

Does anyone have any ideas how to bring it to life?

Thanks in advance!

It seems that nobody ever seen this... Ok, going to flash through JTAG )) God bless me...

Ok. I did the exact same flash as you, I should have searched more the forum...

The image we flashed from the official release should maybe be renamed to warn potential "users".

I will also be opening my 691GR to look for a way to reflash the internal storage.

I've opened my router and in another my thread you can find the photos of it!
One of the users told me, that there is no JTAG on my PCB and it seems that the only connection possible is UART. I've already bought USB-TO-UART connector, but didn't have enough time to try...

(Last edited by anton.v.timin on 9 Feb 2015, 13:48)

Reporting the same issue with TEW-691GR and latest version of OpenWRT - Chaos Calmer 15.05
After flashing "openwrt-15.05-ramips-rt3883-tew-691gr-squashfs-factory.bin" and rebooting, device is alive, but all ports seem not visible by firmware, even LEDs show reaction to incoming packets.
Entering Failsafe mode doesn't help, device easily goes into this mode by pressing WPS button after power-on, but completely no network activity shown on ports.
Seems that CC 15.05 has the same unfixed bug with a net driver.
Any comments?

Its been a while since i have had to recover a router, but I believe the following methods should still work using safemode...

I am sure someone will correct me if I am wrong ...

SAFEMODE RECOVERY

Recovery Using Ubuntu

1. log into router using safemode

2. issue the mount root command ..

mount_root

3 . change to the tmp directory ..

 cd /tmp

4. use scp to load a working bin to the tmp directory from your ubuntu machine ..

 scp <username>@<ip of ubuntu machine>:/path/to/good.bin ./

5. then use sysupgrade to write the good bin ..

sysupgrade -n good.bin

Recover Using Windows with winscp
** I use putty as a terminal **

1. log into router in safemode

2. mount root then set a password ..

mount_root
passwd
<enter password and press enter, do this 2 times >

3. issue the following cmds ..

touch jffs2 
touch root 
/etc/init.d/dropbear start

4. start winscp and connect to router using the following settings ..

Protocol: SCP
Host: 192.168.1.1 
Port: 22 
User: root 
Password: <your password>

5. use scp to click and drag the good.bin to the tmp directory of the router

6. from the safemood terminal cd to the tmp directory ..

 cd /tmp

7. use sysupgrade to write the good.bin ..

sysupgrade -n good.bin

hope this helps wink

(Last edited by hostle19 on 3 Oct 2015, 16:32)

Dear hostle19,
thanks for the info, BUT even in failsafe mode this router doesn't see its LAN-ports ))) No way to connect to it except UART.

my bad, i thought it was mentioned that these units were accessible via safe mode.

(Last edited by hostle19 on 4 Oct 2015, 03:57)

No way smile
Surprised that CC release still having this bug

I might have found the issue for the failing switch initialisation.

Since the TEW-691GR support is broken for a long time, there might be more issues. If possible attach a full bootlog.

(Last edited by mkresin on 20 Aug 2016, 11:00)

Brilliant! The lan ports are alive smile smile

Non-working lan ports fixed by @mkresin.

Goto http://lede-project.org and find latest snapshot.

The snapshot is commandline-only but just do:
# opkg update
# opkg install luci

The wireless configuration of luci isn't working atm. so again use commandline:

http://www.lede-project.org/docs/uci.html
http://www.lede-project.org/docs/uci_wireless.html

I have no idea if the lan port fix will end up in OpenWRT also.

Non-working luci reported in http://github.com/openwrt/luci/issues/780

(Last edited by n8b on 22 Aug 2016, 19:28)

n8b wrote:

The wireless configuration of luci isn't working atm.

Fixed in LEDE build r1442 cool

The discussion might have continued from here.