Bricked my ASUS RT-N16

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3, 4, 5, 6  Next
Author Message
gatorback
DD-WRT User


Joined: 04 Feb 2007
Posts: 333
Location: Fountain of Youth

PostPosted: Sat Jul 09, 2011 18:17    Post subject: Firefox Reply with quote
I made the mistake of using Firefox once and flashed the router (54GL) to behave unrecoverably. Lesson learned. No Firefox when flashing \ configuring DD-WRT. IE8 flashed my ASUS RTN16.

If anyone has used IE9 to successfully flash, please post details (hardware, DD-WRT version etc.)

IE9 was different enough from IE8 that it does not work with a customer's DVR / Camera system, so I am not inclined to flash anything with IE9, unless someone can confirm IE9 is OK to use.

_________________
My Routers | RT-N16 Wiki | RT-N16 Mods
Peacock Flashing | Wireless N Conf | Linking Routers |
DD-WRT Wiki | DD-WRT Builds | Broadcom FAQ| QoS| OTRW


Last edited by gatorback on Sat Jul 09, 2011 23:02; edited 2 times in total
Sponsor
curtiplas
DD-WRT Novice


Joined: 04 Jul 2011
Posts: 8

PostPosted: Sat Jul 09, 2011 18:27    Post subject: Reply with quote
Yeah I used IE, but IE 9... :/
MarcusXP
DD-WRT Novice


Joined: 04 Aug 2011
Posts: 27

PostPosted: Fri Aug 05, 2011 21:48    Post subject: Reply with quote
Anyone knows the exact steps to bring the router to recovery mode?
I tried using the reset button and the red button, but it seems that it doesn't stay in recovery mode more than 1-2 seconds (the power led blinking for short while only), then it goes back to a state where it cannot be accessed using any IP address.
It can be ping-ed to 192.168.1.1 on the duration of 1-2 seconds while the power led is blinking, but then it times-out.
Anyone knows how can I fix it? I am trying to upload the firmware, but if it doesn't stay in recovery mode, I don't know what else I can do..
TheDuke
DD-WRT Novice


Joined: 11 Dec 2006
Posts: 8

PostPosted: Fri Nov 04, 2011 17:38    Post subject: Reply with quote
Part 1 - fixed see third post
Well stupid should have left well enough alone. Flashed unit with the mini build, then the dd-wrt.v24-14896_NEWD-2_K2.6_big, everything was ok, then I decided to put the newest dd-wrt.v24-14929_NEWD-2_K2.6_big-e2000 and she bricked on me.

Did the WPS reset couldn't ping it, did the actual reset couldn't ping it.

Unplugged router for the night, woke up next day did the wds still nada (no ping), then hit reset holding it in while unit was unplugged, then still holding plugged it in, got the power light flashing.

Unit could be pinged so used WinAgents TFTP Client to transfer file, everything ok on transfer. Let unit sit, still no access, tried to ping couldn't ping, hit reset button, unit flashed, then went solid got a ping then could access gui. reset things to default, checked out features everything is alright.


Last edited by TheDuke on Fri Nov 04, 2011 18:11; edited 1 time in total
TheDuke
DD-WRT Novice


Joined: 11 Dec 2006
Posts: 8

PostPosted: Fri Nov 04, 2011 17:40    Post subject: Reply with quote
Part 2

Now not one to run away from a simple ooops, I go to do things again.

I go to flash unit (with IE) with the mini ddwrt. It completes, and re-opens the gui and and I'm at the stock asus interface. I refresh, still the same.

I disconnect router, hold wds, plug in power, power light flashing I tftp the mini build over, everything is okay.

Now I am at a blinking power light, I let it sit, it goes solid, no wifi light on, can not access router by gui, and can not ping router.

I go oh oh, power unit off, hold wds and power on get blinking power light, able to ping unit, I tftp stock asus firmware. Transfer is okay with no errors.

light goes solid after a bit, but still no wifi light and can not ping unit. I power unit off, then power back on and I am 1 hour later still at a blinking power light and I can ping the router.

Ideas ?


Last edited by TheDuke on Fri Nov 04, 2011 18:09; edited 1 time in total
TheDuke
DD-WRT Novice


Joined: 11 Dec 2006
Posts: 8

PostPosted: Fri Nov 04, 2011 18:05    Post subject: Reply with quote
Update
Part 3
Alright, I powered unit down, let it sit for 5 minutes, held wds button while plugging in power, continued to hold wds button for over 30 seconds, power light blinking rapidly, released button, then tftp'd stock asus firmware to unit.

Transfer went okay, I let it sit, did nothing, power led blinked slowly, then after w hile it came on solid, I went had a cigarette, came back, pinged got got half replies. I powered unit off, let it sit for 5 then I powered back on , and let it sit.

Poof, everything back to normal.
JuiciPackets
DD-WRT User


Joined: 26 Jan 2011
Posts: 60

PostPosted: Sun Dec 04, 2011 22:20    Post subject: Looks like I need some help, too :( Reply with quote
Hello dd-wrt gurus

I have a bit of a problem with an RT-N16 that served me well for almost an entire year... it now seems truly bricked and I really hope somebody can point me in the right direction.

I was away for a week and when I returned I found my WiFi SSID gone. My USB memory stick's LED was off so my first thought was that it was finally wrecked (I run OTRW from it with logging on it). The USB memory stick was fine (I can use it on the laptop without any issues) but on a closer look I realised that my RT-N16 was running with the default dd-wrt settings (i.e. an unsecured "dd-wrt" SSID; it would also ask me to set the root password when I tried to connect to the web interface)! I assume this may have had to do with the frequent power outages here (at least 1-2 every day).

Now this is where I think I messed things up more Sad - I connected to the router via telnet, I used "nvram unset ..." to unset all variables one by one (yeah, I now recognize I should have used "nvram erase" instead, but after just 6 hours slept in 2 days, followed by a transatlantic flight fighting a really bad cold things didn't seem so obvious at the time, especially when "nvram"'s syntax help doesn't list this command... Sad ), I used a recent OTRW-generated backup of all nvram variables (restore script ending in ".11202011.all.sh"), I commented the last line in it ("nvram commit") just to get a chance to do a last "nvram show" before committing, and then I did a "nvram comitt" (YES, with this exact spelling mistake - which, BTW, did not return any error...), followed by "reboot".

You can find below the sequence of commands, with some non-relevant output removed:

Code:

root@DD-WRT:~# nvram 2>/dev/null show | cut -d= -f1 | awk '{ print "nvram unset "$1 }' | while read i
> do
> $i
> done
root@DD-WRT:~#
root@DD-WRT:~# nvram show
size: 20 bytes (32748 left)
root@DD-WRT:~#
root@DD-WRT:~# ./set         <-- this was the restore script for all nvram variables generated by OTRW
Write variables
Save variables to nvram      <-- just a reminder, I commented out the last line "nvram commit"
root@DD-WRT:~#
root@DD-WRT:~# nvram show
br1_netmask=255.255.255.0
filter_dport_grp3=
............................ <-- non-relevant output omitted
vlan1_nat=1
wl0_wds9_ipaddr=
size: 29701 bytes (3067 left)
root@DD-WRT:~#
root@DD-WRT:~# nvram comitt  <-- with this exact spelling mistake...
root@DD-WRT:~#
root@DD-WRT:~# nvram show
br1_netmask=255.255.255.0
filter_dport_grp3=
............................ <-- non-relevant output omitted
vlan1_nat=1
wl0_wds9_ipaddr=
size: 29701 bytes (3067 left)
root@DD-WRT:~#
root@DD-WRT:~# nvram
usage: nvram [get name] [set name=value] [unset name] [show] [backup filename] [restore filename]
root@DD-WRT:~#
root@DD-WRT:~# sync
root@DD-WRT:~# sync
root@DD-WRT:~# reboot
Connection closed by foreign host.



From this point on I could not access my router no matter what I tried - 30/30/30 hard resets, pressing "Restore" while plugging the power in, leaving it unpowered over night and trying again in the morning, manually setting my laptop's Ethernet interface to 192.168.1.10 and trying to ping 192.168.1.1 ... nothing worked. When I try a 30/30/30 procedure (using any of the 2 buttons - red "WPS" or black "Restore") and I plug the power back on all 5 LEDs for LAN and WAN come on for about a second or two, then only the LED for the LAN port where the laptop is connected remains on and that's it... None of the Asus utilities from the CD even detects the router even though the router's LED lights for the ports show the activity (packets being sent or received) and ethtool on the laptop says I'm connected:

Code:

# ethtool eth0
Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: g
        Wake-on: g
        Current message level: 0x000000ff (255)
        Link detected: yes


Any ideas what I could try next? The router can't be "dead" hardware-wise, it was still working with the default configuration when I came back and messed it up Sad Any suggestions gladly welcomed.

Cheers!
gatorback
DD-WRT User


Joined: 04 Feb 2007
Posts: 333
Location: Fountain of Youth

PostPosted: Mon Dec 05, 2011 0:56    Post subject: Reply with quote
@juicipackets: others may provide you with better guidnance, however, in the absence of any other guidance, I would consider reflashing the firmware and reinstalling OTRW.

A fair number of cases take too long to solve and it is quicker to resolve the problem by starting from the beginning.

_________________
My Routers | RT-N16 Wiki | RT-N16 Mods
Peacock Flashing | Wireless N Conf | Linking Routers |
DD-WRT Wiki | DD-WRT Builds | Broadcom FAQ| QoS| OTRW
JuiciPackets
DD-WRT User


Joined: 26 Jan 2011
Posts: 60

PostPosted: Mon Dec 05, 2011 1:06    Post subject: Thanks, but Reply with quote
Am I missing something? How do you see me reflashing the firmware and reinstalling OTRW if the router is bricked?


Info according to note 6 of the peacock thread:

Asus RT-N16, power supply ok, only LAN address it ever had 192.168.1.1
Only one LAN port directly connected to my laptop running Linux (kernel 2.6), no other connections from/to router

Quote:

post the exact message you get from your initial ping attempt:


Code:

# ifconfig eth0 192.168.1.10
# ifconfig eth0 | grep "inet addr"
          inet addr:192.168.1.10  Bcast:192.168.1.255  Mask:255.255.255.0
# ping -c 1 192.168.1.10
PING 192.168.1.10 (192.168.1.10) 56(84) bytes of data.
64 bytes from 192.168.1.10: icmp_seq=1 ttl=64 time=0.078 ms

--- 192.168.1.10 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.078/0.078/0.078/0.000 ms
# ping -c 10 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.10 icmp_seq=2 Destination Host Unreachable
From 192.168.1.10 icmp_seq=3 Destination Host Unreachable
From 192.168.1.10 icmp_seq=4 Destination Host Unreachable
From 192.168.1.10 icmp_seq=6 Destination Host Unreachable
From 192.168.1.10 icmp_seq=7 Destination Host Unreachable
From 192.168.1.10 icmp_seq=8 Destination Host Unreachable
From 192.168.1.10 icmp_seq=9 Destination Host Unreachable
From 192.168.1.10 icmp_seq=10 Destination Host Unreachable

--- 192.168.1.1 ping statistics ---
10 packets transmitted, 0 received, +8 errors, 100% packet loss, time 8999ms
, pipe 3
# arp -a
dd-wrt (192.168.1.1) at <incomplete> on eth0



Quote:

If you get "destination host unreachable", you likely have your computer on a different sub-network than the one you are trying to ping. Check to make sure that you have your computer set to the same static IP subnet (eg.192.168.1.10) as the address you are trying to ping.
Some routers are 192.168.10.1 and some are 192.168.1.245


Code:

# ifconfig eth0 192.168.10.10
# ifconfig eth0 | grep "inet addr"
          inet addr:192.168.10.10  Bcast:192.168.10.255  Mask:255.255.255.0
# ping -c 1 192.168.10.10
PING 192.168.10.10 (192.168.10.10) 56(84) bytes of data.
64 bytes from 192.168.10.10: icmp_seq=1 ttl=64 time=0.086 ms

--- 192.168.10.10 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.086/0.086/0.086/0.000 ms
# ping -c 10 192.168.10.1
PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data.
From 192.168.10.10 icmp_seq=2 Destination Host Unreachable
From 192.168.10.10 icmp_seq=3 Destination Host Unreachable
From 192.168.10.10 icmp_seq=4 Destination Host Unreachable
From 192.168.10.10 icmp_seq=6 Destination Host Unreachable
From 192.168.10.10 icmp_seq=7 Destination Host Unreachable
From 192.168.10.10 icmp_seq=8 Destination Host Unreachable
From 192.168.10.10 icmp_seq=9 Destination Host Unreachable
From 192.168.10.10 icmp_seq=10 Destination Host Unreachable

--- 192.168.10.1 ping statistics ---
10 packets transmitted, 0 received, +8 errors, 100% packet loss, time 8999ms
, pipe 3
# arp -a
? (192.168.10.1) at <incomplete> on eth0
#



# ifconfig eth0 192.168.1.24
# ifconfig eth0 | grep "inet addr"
          inet addr:192.168.1.24  Bcast:192.168.1.255  Mask:255.255.255.0
# ping -c 1 192.168.1.24
PING 192.168.1.24 (192.168.1.24) 56(84) bytes of data.
64 bytes from 192.168.1.24: icmp_seq=1 ttl=64 time=0.088 ms

--- 192.168.1.24 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.088/0.088/0.088/0.000 ms
# ping -c 10 192.168.1.245
PING 192.168.1.245 (192.168.1.245) 56(84) bytes of data.
From 192.168.1.24 icmp_seq=2 Destination Host Unreachable
From 192.168.1.24 icmp_seq=3 Destination Host Unreachable
From 192.168.1.24 icmp_seq=4 Destination Host Unreachable
From 192.168.1.24 icmp_seq=6 Destination Host Unreachable
From 192.168.1.24 icmp_seq=7 Destination Host Unreachable
From 192.168.1.24 icmp_seq=8 Destination Host Unreachable
From 192.168.1.24 icmp_seq=9 Destination Host Unreachable
From 192.168.1.24 icmp_seq=10 Destination Host Unreachable

--- 192.168.1.245 ping statistics ---
10 packets transmitted, 0 received, +8 errors, 100% packet loss, time 8999ms
, pipe 3
# arp -a
? (192.168.1.245) at <incomplete> on eth0



Quote:

the message you get during and after a power cycle:


Code:

# ifconfig eth0 192.168.1.10
# ifconfig eth0 | grep "inet addr"
          inet addr:192.168.1.10  Bcast:192.168.1.255  Mask:255.255.255.0
# ping -c 1 192.168.1.10
PING 192.168.1.10 (192.168.1.10) 56(84) bytes of data.
64 bytes from 192.168.1.10: icmp_seq=1 ttl=64 time=0.086 ms

--- 192.168.1.10 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.086/0.086/0.086/0.000 ms
# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.10 icmp_seq=2 Destination Host Unreachable
From 192.168.1.10 icmp_seq=3 Destination Host Unreachable
From 192.168.1.10 icmp_seq=4 Destination Host Unreachable
From 192.168.1.10 icmp_seq=6 Destination Host Unreachable
From 192.168.1.10 icmp_seq=7 Destination Host Unreachable
From 192.168.1.10 icmp_seq=8 Destination Host Unreachable
From 192.168.1.10 icmp_seq=10 Destination Host Unreachable
From 192.168.1.10 icmp_seq=11 Destination Host Unreachable
From 192.168.1.10 icmp_seq=12 Destination Host Unreachable
From 192.168.1.10 icmp_seq=14 Destination Host Unreachable
From 192.168.1.10 icmp_seq=15 Destination Host Unreachable
From 192.168.1.10 icmp_seq=16 Destination Host Unreachable
From 192.168.1.10 icmp_seq=18 Destination Host Unreachable
From 192.168.1.10 icmp_seq=19 Destination Host Unreachable
From 192.168.1.10 icmp_seq=20 Destination Host Unreachable
From 192.168.1.10 icmp_seq=22 Destination Host Unreachable
From 192.168.1.10 icmp_seq=23 Destination Host Unreachable
From 192.168.1.10 icmp_seq=24 Destination Host Unreachable
From 192.168.1.10 icmp_seq=26 Destination Host Unreachable
From 192.168.1.10 icmp_seq=27 Destination Host Unreachable
From 192.168.1.10 icmp_seq=28 Destination Host Unreachable
From 192.168.1.10 icmp_seq=30 Destination Host Unreachable
From 192.168.1.10 icmp_seq=31 Destination Host Unreachable
From 192.168.1.10 icmp_seq=32 Destination Host Unreachable
From 192.168.1.10 icmp_seq=34 Destination Host Unreachable
From 192.168.1.10 icmp_seq=35 Destination Host Unreachable
From 192.168.1.10 icmp_seq=36 Destination Host Unreachable
From 192.168.1.10 icmp_seq=38 Destination Host Unreachable
From 192.168.1.10 icmp_seq=39 Destination Host Unreachable
From 192.168.1.10 icmp_seq=40 Destination Host Unreachable
From 192.168.1.10 icmp_seq=42 Destination Host Unreachable
From 192.168.1.10 icmp_seq=43 Destination Host Unreachable
From 192.168.1.10 icmp_seq=44 Destination Host Unreachable
From 192.168.1.10 icmp_seq=46 Destination Host Unreachable
From 192.168.1.10 icmp_seq=47 Destination Host Unreachable
From 192.168.1.10 icmp_seq=48 Destination Host Unreachable
From 192.168.1.10 icmp_seq=50 Destination Host Unreachable
From 192.168.1.10 icmp_seq=51 Destination Host Unreachable
From 192.168.1.10 icmp_seq=52 Destination Host Unreachable

--- 192.168.1.1 ping statistics ---
55 packets transmitted, 0 received, +39 errors, 100% packet loss, time 53999ms
, pipe 3
# arp -a
dd-wrt (192.168.1.1) at <incomplete> on eth0



Quote:

and the message you get when pinging during and after a hard reset:


30/30/30 procedure completed using the red "WPS" button:

Code:

# ifconfig eth0 192.168.1.10
# ifconfig eth0 | grep "inet addr"
          inet addr:192.168.1.10  Bcast:192.168.1.255  Mask:255.255.255.0
# ping -c 1 192.168.1.10
PING 192.168.1.10 (192.168.1.10) 56(84) bytes of data.
64 bytes from 192.168.1.10: icmp_seq=1 ttl=64 time=0.082 ms

--- 192.168.1.10 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.082/0.082/0.082/0.000 ms
# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.10 icmp_seq=2 Destination Host Unreachable
From 192.168.1.10 icmp_seq=3 Destination Host Unreachable
From 192.168.1.10 icmp_seq=4 Destination Host Unreachable
From 192.168.1.10 icmp_seq=6 Destination Host Unreachable
From 192.168.1.10 icmp_seq=7 Destination Host Unreachable
From 192.168.1.10 icmp_seq=8 Destination Host Unreachable
From 192.168.1.10 icmp_seq=10 Destination Host Unreachable
From 192.168.1.10 icmp_seq=11 Destination Host Unreachable
From 192.168.1.10 icmp_seq=12 Destination Host Unreachable
From 192.168.1.10 icmp_seq=14 Destination Host Unreachable
From 192.168.1.10 icmp_seq=15 Destination Host Unreachable
From 192.168.1.10 icmp_seq=16 Destination Host Unreachable
From 192.168.1.10 icmp_seq=18 Destination Host Unreachable
From 192.168.1.10 icmp_seq=19 Destination Host Unreachable
From 192.168.1.10 icmp_seq=20 Destination Host Unreachable
From 192.168.1.10 icmp_seq=22 Destination Host Unreachable
From 192.168.1.10 icmp_seq=23 Destination Host Unreachable
From 192.168.1.10 icmp_seq=24 Destination Host Unreachable
From 192.168.1.10 icmp_seq=26 Destination Host Unreachable
From 192.168.1.10 icmp_seq=27 Destination Host Unreachable
From 192.168.1.10 icmp_seq=28 Destination Host Unreachable
From 192.168.1.10 icmp_seq=30 Destination Host Unreachable
From 192.168.1.10 icmp_seq=31 Destination Host Unreachable
From 192.168.1.10 icmp_seq=32 Destination Host Unreachable
From 192.168.1.10 icmp_seq=34 Destination Host Unreachable
From 192.168.1.10 icmp_seq=35 Destination Host Unreachable
From 192.168.1.10 icmp_seq=36 Destination Host Unreachable
From 192.168.1.10 icmp_seq=38 Destination Host Unreachable
From 192.168.1.10 icmp_seq=39 Destination Host Unreachable
From 192.168.1.10 icmp_seq=40 Destination Host Unreachable
From 192.168.1.10 icmp_seq=42 Destination Host Unreachable
From 192.168.1.10 icmp_seq=43 Destination Host Unreachable
From 192.168.1.10 icmp_seq=44 Destination Host Unreachable
From 192.168.1.10 icmp_seq=46 Destination Host Unreachable
From 192.168.1.10 icmp_seq=47 Destination Host Unreachable
From 192.168.1.10 icmp_seq=48 Destination Host Unreachable
From 192.168.1.10 icmp_seq=50 Destination Host Unreachable
From 192.168.1.10 icmp_seq=51 Destination Host Unreachable
From 192.168.1.10 icmp_seq=52 Destination Host Unreachable
From 192.168.1.10 icmp_seq=54 Destination Host Unreachable
From 192.168.1.10 icmp_seq=55 Destination Host Unreachable
From 192.168.1.10 icmp_seq=56 Destination Host Unreachable
From 192.168.1.10 icmp_seq=58 Destination Host Unreachable
From 192.168.1.10 icmp_seq=59 Destination Host Unreachable
From 192.168.1.10 icmp_seq=60 Destination Host Unreachable
From 192.168.1.10 icmp_seq=62 Destination Host Unreachable
From 192.168.1.10 icmp_seq=63 Destination Host Unreachable
From 192.168.1.10 icmp_seq=64 Destination Host Unreachable
From 192.168.1.10 icmp_seq=66 Destination Host Unreachable
From 192.168.1.10 icmp_seq=67 Destination Host Unreachable
From 192.168.1.10 icmp_seq=68 Destination Host Unreachable
From 192.168.1.10 icmp_seq=70 Destination Host Unreachable
From 192.168.1.10 icmp_seq=71 Destination Host Unreachable
From 192.168.1.10 icmp_seq=72 Destination Host Unreachable
From 192.168.1.10 icmp_seq=74 Destination Host Unreachable
From 192.168.1.10 icmp_seq=75 Destination Host Unreachable
From 192.168.1.10 icmp_seq=76 Destination Host Unreachable
From 192.168.1.10 icmp_seq=78 Destination Host Unreachable
From 192.168.1.10 icmp_seq=79 Destination Host Unreachable
From 192.168.1.10 icmp_seq=80 Destination Host Unreachable
From 192.168.1.10 icmp_seq=82 Destination Host Unreachable
From 192.168.1.10 icmp_seq=83 Destination Host Unreachable
From 192.168.1.10 icmp_seq=84 Destination Host Unreachable
From 192.168.1.10 icmp_seq=86 Destination Host Unreachable
From 192.168.1.10 icmp_seq=87 Destination Host Unreachable
From 192.168.1.10 icmp_seq=88 Destination Host Unreachable
From 192.168.1.10 icmp_seq=90 Destination Host Unreachable
From 192.168.1.10 icmp_seq=91 Destination Host Unreachable
From 192.168.1.10 icmp_seq=92 Destination Host Unreachable
From 192.168.1.10 icmp_seq=94 Destination Host Unreachable
From 192.168.1.10 icmp_seq=95 Destination Host Unreachable
From 192.168.1.10 icmp_seq=96 Destination Host Unreachable
From 192.168.1.10 icmp_seq=98 Destination Host Unreachable
From 192.168.1.10 icmp_seq=99 Destination Host Unreachable
From 192.168.1.10 icmp_seq=100 Destination Host Unreachable
From 192.168.1.10 icmp_seq=102 Destination Host Unreachable
From 192.168.1.10 icmp_seq=103 Destination Host Unreachable
From 192.168.1.10 icmp_seq=104 Destination Host Unreachable
From 192.168.1.10 icmp_seq=106 Destination Host Unreachable
From 192.168.1.10 icmp_seq=107 Destination Host Unreachable
From 192.168.1.10 icmp_seq=108 Destination Host Unreachable
From 192.168.1.10 icmp_seq=110 Destination Host Unreachable
From 192.168.1.10 icmp_seq=111 Destination Host Unreachable
From 192.168.1.10 icmp_seq=112 Destination Host Unreachable
From 192.168.1.10 icmp_seq=114 Destination Host Unreachable
From 192.168.1.10 icmp_seq=115 Destination Host Unreachable
From 192.168.1.10 icmp_seq=116 Destination Host Unreachable

--- 192.168.1.1 ping statistics ---
118 packets transmitted, 0 received, +87 errors, 100% packet loss, time 116999ms
, pipe 3



Quote:

Also post what each light in the front of the router is doing,


It does NOT matter if I press any button (red "WPS" or black "Restore"), the LEDs act like this:
- When the router is powered on, only the LAN2 LED is on (where I have the laptop connected); the LED flashes briefly once per second as the ping command sends ICMP echo-request packets
- When the power is unplugged all LEDs are off (duh Smile )
- When I plug back the power only 5 LEDs (4xLAN + 1xWAN) light for a second or two, then all LEDs are off for a second or two, then only LAN2 comes back on; from this point on it acts as describes at the first point above


Quote:

i. If there are no ttl= responses, do a hard reset on your router, while the pings continue. Again. watch for any ping responses. If you get none, you likely need to jtag or use one of the recovery methods listed below in this note. Your router is bricked.


Sad
JuiciPackets
DD-WRT User


Joined: 26 Jan 2011
Posts: 60

PostPosted: Mon Dec 05, 2011 19:23    Post subject: Reply with quote
barryware wrote:
jtag is not supported just yet even though the device has the connection(s) for it.. Only serial can be used.


@barryware: I'm aware this is now quite old info but I am just trying to figure out the truth Smile - is JTAG supported on Asus RT-N16? From the following 2 links I suppose it is, can anybody confirm please? Thanks!

http://www.dd-wrt.com/wiki/index.php/JTAG_pinouts#Asus_RT-N16

http://www.dd-wrt.com/phpBB2/files/basis_for_making_jtag_cable_770.jpg

Also, http://www.dd-wrt.com/wiki/index.php/JTAG says "To jtag a router you can download a copy of tornado's program from the tornado subdirectory: ftp://dd-wrt.com/others/tornado/jtag/ " but that directory doesn't exist anymore. I also found http://www.dd-wrt.com/phpBB2/viewtopic.php?t=22655 (posted on Nov 04, 2007) that says "I have decided that after working on Tjtag for almost 6 years, and very few donations, that tjtag will only be available from http://tjtag.com". However on that site I could not find the linux source code I was looking for and I got the feeling that tjtag will only work with the TIAO Universal jtag adapter (I may be of course wrong).

So can anybody please point me to a working JTAG software for Linux that I can use to debrick my RT-N16? I'm new to all this JTAG stuff and I am confused by old posts and so on.

Cheers!
raftguide3r
DD-WRT Novice


Joined: 06 Dec 2011
Posts: 4

PostPosted: Tue Dec 06, 2011 22:10    Post subject: Also bricked my rt-n16 Reply with quote
Go a new router last week and loaded with dd-wrt.v24-14929_NEWD-2_K2.6_big.bin (flashed the trx version first in Asus web ui)

After configuring everything worked fine for a few days. On Sunday my wifes laptop dropped wireless while she was surfing the web. I attempted to log into the router from a hard wired computer to reboot but couldn't connect to the dd-wrt web interface.

Unplugged and plugged back in. No wireless, no Web GUI, couldn't ping 192.168.1.1, power led not on, wireless led not on.

I can't seem to get the router into recovery. ping -t 192.168.1.1 returns request timeout or Destination host unreachable when plugging in. I've tried holding the WPS button while plugging in, the restore button while plugging in, and both while plugging in. I've tried letting it sit unplugged for 24 hours and repeating.

I've tried tftp and the Asus firmware restoration tool.

Not sure what else to try. I don't think I can return it to Amazon since I already cut the UPC off the box for the mail in rebate. Sad

Most of what I've found about bricked routers it happens when flashing, my router flashed fine and was up and running for days without any problems... now I have an $80 week old brick.

I assume dd-wrt voids the warranty. What should I try next.
barryware
DD-WRT Guru


Joined: 26 Jan 2008
Posts: 12736
Location: Behind The Reset Button

PostPosted: Tue Dec 06, 2011 22:15    Post subject: Re: Also bricked my rt-n16 Reply with quote
raftguide3r wrote:
Go a new router last week and loaded with dd-wrt.v24-14929_NEWD-2_K2.6_big.bin (flashed the trx version first in Asus web ui)

After configuring everything worked fine for a few days. On Sunday my wifes laptop dropped wireless while she was surfing the web. I attempted to log into the router from a hard wired computer to reboot but couldn't connect to the dd-wrt web interface.

Unplugged and plugged back in. No wireless, no Web GUI, couldn't ping 192.168.1.1, power led not on, wireless led not on.

I can't seem to get the router into recovery. ping -t 192.168.1.1 returns request timeout or Destination host unreachable when plugging in. I've tried holding the WPS button while plugging in, the restore button while plugging in, and both while plugging in. I've tried letting it sit unplugged for 24 hours and repeating.

I've tried tftp and the Asus firmware restoration tool.

Not sure what else to try. I don't think I can return it to Amazon since I already cut the UPC off the box for the mail in rebate. Sad

Most of what I've found about bricked routers it happens when flashing, my router flashed fine and was up and running for days without any problems... now I have an $80 week old brick.

I assume dd-wrt voids the warranty. What should I try next.


case of beer says your power supply took a crap.

_________________
[Moderator Deleted] Shocked
raftguide3r
DD-WRT Novice


Joined: 06 Dec 2011
Posts: 4

PostPosted: Tue Dec 06, 2011 22:19    Post subject: Re: Also bricked my rt-n16 Reply with quote
barryware wrote:
raftguide3r wrote:
Go a new router last week and loaded with dd-wrt.v24-14929_NEWD-2_K2.6_big.bin (flashed the trx version first in Asus web ui)

After configuring everything worked fine for a few days. On Sunday my wifes laptop dropped wireless while she was surfing the web. I attempted to log into the router from a hard wired computer to reboot but couldn't connect to the dd-wrt web interface.

Unplugged and plugged back in. No wireless, no Web GUI, couldn't ping 192.168.1.1, power led not on, wireless led not on.

I can't seem to get the router into recovery. ping -t 192.168.1.1 returns request timeout or Destination host unreachable when plugging in. I've tried holding the WPS button while plugging in, the restore button while plugging in, and both while plugging in. I've tried letting it sit unplugged for 24 hours and repeating.

I've tried tftp and the Asus firmware restoration tool.

Not sure what else to try. I don't think I can return it to Amazon since I already cut the UPC off the box for the mail in rebate. Sad

Most of what I've found about bricked routers it happens when flashing, my router flashed fine and was up and running for days without any problems... now I have an $80 week old brick.

I assume dd-wrt voids the warranty. What should I try next.


case of beer says your power supply took a crap.


I forgot to mention, the LAN/WAN leds come on and go off when pluggin in... then any LAN led with a cable plugged in with flash randomaly like LAN LED's tend to... could it still be the power supply?
barryware
DD-WRT Guru


Joined: 26 Jan 2008
Posts: 12736
Location: Behind The Reset Button

PostPosted: Tue Dec 06, 2011 22:26    Post subject: Re: Also bricked my rt-n16 Reply with quote
raftguide3r wrote:
barryware wrote:
raftguide3r wrote:
Go a new router last week and loaded with dd-wrt.v24-14929_NEWD-2_K2.6_big.bin (flashed the trx version first in Asus web ui)

After configuring everything worked fine for a few days. On Sunday my wifes laptop dropped wireless while she was surfing the web. I attempted to log into the router from a hard wired computer to reboot but couldn't connect to the dd-wrt web interface.

Unplugged and plugged back in. No wireless, no Web GUI, couldn't ping 192.168.1.1, power led not on, wireless led not on.

I can't seem to get the router into recovery. ping -t 192.168.1.1 returns request timeout or Destination host unreachable when plugging in. I've tried holding the WPS button while plugging in, the restore button while plugging in, and both while plugging in. I've tried letting it sit unplugged for 24 hours and repeating.

I've tried tftp and the Asus firmware restoration tool.

Not sure what else to try. I don't think I can return it to Amazon since I already cut the UPC off the box for the mail in rebate. Sad

Most of what I've found about bricked routers it happens when flashing, my router flashed fine and was up and running for days without any problems... now I have an $80 week old brick.

I assume dd-wrt voids the warranty. What should I try next.


case of beer says your power supply took a crap.


I forgot to mention, the LAN/WAN leds come on and go off when pluggin in... then any LAN led with a cable plugged in with flash randomaly like LAN LED's tend to... could it still be the power supply?


I retract my statement now seeing that the lan lights behave properly but I have said it a million times.. when a router is happily running and takes a crap out of no where, it usually indicates a hardware failure (not all the time though), and power supply failures are common.

_________________
[Moderator Deleted] Shocked
raftguide3r
DD-WRT Novice


Joined: 06 Dec 2011
Posts: 4

PostPosted: Tue Dec 06, 2011 22:32    Post subject: Re: Also bricked my rt-n16 Reply with quote
barryware wrote:
raftguide3r wrote:
barryware wrote:
raftguide3r wrote:
Go a new router last week and loaded with dd-wrt.v24-14929_NEWD-2_K2.6_big.bin (flashed the trx version first in Asus web ui)

After configuring everything worked fine for a few days. On Sunday my wifes laptop dropped wireless while she was surfing the web. I attempted to log into the router from a hard wired computer to reboot but couldn't connect to the dd-wrt web interface.

Unplugged and plugged back in. No wireless, no Web GUI, couldn't ping 192.168.1.1, power led not on, wireless led not on.

I can't seem to get the router into recovery. ping -t 192.168.1.1 returns request timeout or Destination host unreachable when plugging in. I've tried holding the WPS button while plugging in, the restore button while plugging in, and both while plugging in. I've tried letting it sit unplugged for 24 hours and repeating.

I've tried tftp and the Asus firmware restoration tool.

Not sure what else to try. I don't think I can return it to Amazon since I already cut the UPC off the box for the mail in rebate. Sad

Most of what I've found about bricked routers it happens when flashing, my router flashed fine and was up and running for days without any problems... now I have an $80 week old brick.

I assume dd-wrt voids the warranty. What should I try next.


case of beer says your power supply took a crap.


I forgot to mention, the LAN/WAN leds come on and go off when pluggin in... then any LAN led with a cable plugged in with flash randomaly like LAN LED's tend to... could it still be the power supply?


I retract my statement now seeing that the lan lights behave properly but I have said it a million times.. when a router is happily running and takes a crap out of no where, it usually indicates a hardware failure (not all the time though), and power supply failures are common.


Do you know if Asus will honor a warranty claim on a router that had dd-wrt on it? I assume dd-wrt couldn't have caused the hardware failure, I wasn't overclocking, I didn't change Tx power on wireless.
Goto page Previous  1, 2, 3, 4, 5, 6  Next Display posts from previous:    Page 3 of 6
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum