WRT350N bricked

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3  Next
Author Message
obsydian
DD-WRT Novice


Joined: 05 Jan 2007
Posts: 5

PostPosted: Wed Jul 04, 2007 23:44    Post subject: Reply with quote
I've had something similar happen to me twice. Both times, dd-wrt v24 beta has been running on the router with no problems for about a month or so. Then I go into the web gui to change some setting, and the page will hang after clicking confirm. The router still works, but the gui is unresponsive. When I unplug the router, it bricks with the blinking power led deal. A couple of the port lights come on and flash, but the power led never stops flashing and after a few seconds the computers say no connection.

I tried holding the reset button on back for 30s during powerup, but that doesn't work. I was able to TFTP the v24 wrt350n mini and generic on there, but nothing happens afterwards. If I try to TFTP the stock Linksys firmware (7MB), it gets about 3/4 done before the computer says I've lost the connection. After that, I can still TFTP the dd-wrt mini's, but still no change. Tried two different TFTP programs, and waited various lengths after they say the flash was successful.

After a Best Buy exchange, I'm wary of putting dd-wrt on again until I have a sure way of at least de-bricking. I'm willing to test a few things on the brick I have, so let me know if anyone has some ideas.
Sponsor
obsydian
DD-WRT Novice


Joined: 05 Jan 2007
Posts: 5

PostPosted: Sat Jul 07, 2007 3:12    Post subject: Reply with quote
Anything else I can try to de-brick it?

Thanks!
blueangelzx
DD-WRT Novice


Joined: 08 Jul 2007
Posts: 32

PostPosted: Mon Jul 09, 2007 17:56    Post subject: Reply with quote
Actually i have a similar problem :S installed dd-wrt.v24_mini_wrt350n and didn't work my wireless fine.. then i tried to return to the original firmware that i saw in this topic.. http://www.dd-wrt.com/phpBB2/viewtopic.php?p=95450#95450 after that my router doesn't accept the default password.. i dunno what hapened :S, i know before changed this firmware dd-wrt.v24_mini_wrt350n i make a reset for 30 sec and i restored to default factory.. after that i return to the original firmware wrt350n.bin posted here :S.. now my problem with the password :S, u know how can i solve this? Sad
blueangelzx
DD-WRT Novice


Joined: 08 Jul 2007
Posts: 32

PostPosted: Mon Jul 09, 2007 18:44    Post subject: Reply with quote
Already solved with the help of Rekoil Razz
alowin
DD-WRT Novice


Joined: 09 Jul 2007
Posts: 5

PostPosted: Mon Jul 09, 2007 20:17    Post subject: Same Issues Reply with quote
I had bricked my 350n before and tried all the tricks and nothing worked. Thing is, the wireless was still broadcasting. the router assigned a 169.x.x.x ip and gateway to my computer and that is what thru me for a loop. I used the 169.x.x.x gateway address and walla, I had the routers gui. Was a scary thing to firmware flash over wireles but didn't have a choose. It did work out in the end.

Alowin
srekam
DD-WRT Novice


Joined: 14 Jul 2007
Posts: 14

PostPosted: Sat Jul 14, 2007 4:13    Post subject: About my Debrick WRT350n success history Reply with quote
I success to recovery WRT350N at one week end I'm try many way to debrick jtag tftp via telnet web any thing brick I'm dig around broad and found YES Serial Console YO I use Chip max232 conect to broad G TX RX VCC++ 3V it Work I can connect my router again via Hyperterminal I can see debug message say some thing like firmware corrupted I not good command but I try to use "erase linux" and router automatic restart it and stop waiting for flast i use firmware wrt350n.bin with command "c:\tftp -i 192.168.1.1 PUT wrt350n.bin" now come back OH my God Sorry for my English
lijianch
DD-WRT User


Joined: 14 Jul 2007
Posts: 145

PostPosted: Sat Jul 14, 2007 14:16    Post subject: Re: WRT350N bricked Reply with quote
skorianez wrote:
I just brick my router WRT350N,

When I turn the router on the power LED blinking and nothing happens, I tried to reset, and nothing, I can't even ping 192.168.1.1

What should I do now?
Install serial console to see what messages the give me?
Or go ahead and assembly a JTAG cable and try to unbrick?
Any hint is apreciated.
thanks in advance.


I did the exactly same thing on my WRT350N but I recover it.

You can use windowsxp tftp utility with Linksys official firmware. 1 minutes will be fine. The key part is to get command (exclude the quotes)
"tftp -i 192.168.1.1 PUT code.bin" ready and power off wrt350n

When you plug it on and the power light is blinking, press enter the execute tftp command. You will be fine.
CaScAdE
DD-WRT Guru


Joined: 18 Jun 2006
Posts: 1110
Location: Kiel (54.4247,10.1721)

PostPosted: Mon Aug 13, 2007 16:18    Post subject: Reply with quote
I did the same srekam did...
Different chip used (MAX3232) but worked

The pinout of the serial is the same as for most linksys stuff... The wrt54g-series have it that way, or if the have two of them they are just doubled up...

You will still need a level shifter from TTL Level to PC-Port-Serial, but that is common for such devices. Look around for information about adding a serial port to an WRT54G, it is exactly the same stuff you need...

If you get it then open serial connection and press Ctrl+C during bootup, you will end up in CFE.
there you will have to
nvram set boot_wait=on
nvram commit

and see if it gets pingable again during boot (only for 3secconds, so like always, connect it to a switch, ensure your pc has got 192.168.1.X as ip and do a constant ping [normal in most *nix systems, -t for windoze])
if it is then try uploading firmware the normal tftp-way.
If it ends up in some errors in the serial console about the flash not being verified than try
flash -noheader : flash1.trx
and tftp imidiatly after typing it...

Worked for me.

OpenWrtDocs/Troubleshooting helped a lot



wrt350n-serial-pinout.jpg
 Description:
 Filesize:  166.96 KB
 Viewed:  26357 Time(s)

wrt350n-serial-pinout.jpg



_________________
DD-WRT F.A.Q.

Webcam Kiel
Cyber Sleeper
DD-WRT Novice


Joined: 16 Apr 2008
Posts: 1

PostPosted: Wed Apr 16, 2008 9:38    Post subject: Bricked WRT350N Flashing Green Pwr Light Reply with quote
I had flashing green pwr light on my WRT350N after I attempted the v1.03.7 firmware upgrade from the original v1.03.2. I was now unable to access the GUI via http://192.168.1.1/ I tried several times doing the hard reset with no results. I thought for sure I was out a new router until I performed the following.
This was all performed on a Macbook Pro running OSx v10.5.2

I re-downloaded "WRT350N_1.03.7_US_code.bin" and saved it on my Desktop. I renamed it "code.bin" no quotes.

With the WRT350N powered on and connected to my Mac via LAN port 4 and no WAN cable connected to my Cable Modem, I performed the following:

Opened Terminal
<type> cd Desktop (which took me to my Desktop directory which is where my renamed file "code.bin" is located.)
$ tftp
tftp> verbose (allows you to see respones)
tftp> binary (sets file transfer to octet)
tftp> connect 192.168.1.1
tftp> put (this is the send file command)
(file) code.bin

Here is the response you will get back IF successful.
putting code.bin to 192.168.1.1:code.bin [octet]
Sent 6575104 bytes in 12.1 seconds [4347176 bits/sec]
tftp>

At this point it took about 3 minutes for the flasing green power light to go SOLID GREEN. Just let it sit there for awhile and it "should" go solid green. At that point I was able to access http://192.168.1.1 using the default login/password

I was so happy :)
meex
DD-WRT User


Joined: 26 Dec 2006
Posts: 127
Location: Würzburg, Germany

PostPosted: Tue Apr 22, 2008 22:05    Post subject: Reply with quote
tftp> put code.bin <-- orgianl linksys
putting code.bin to 192.168.1.1:code.bin [octet]
Error code 3: transfer cancelled
Sent 3801088 bytes in 5.7 seconds [5334860 bits/sec]

tftp> put code.bin <-- dd.wrt mini wrt350n
putting code.bin to 192.168.1.1:code.bin [octet]
Sent 2798592 bytes in 5.3 seconds [4224290 bits/sec]
tftp>



but after 3 min's it does still blinking, i waited 10 minutes without success...

and now?

_________________
AcADIeN
DD-WRT Novice


Joined: 29 Oct 2008
Posts: 1

PostPosted: Wed Oct 29, 2008 11:27    Post subject: Brick Reply with quote
Yeah I did brick my wrt350n v1 yesterday (power led blinking without stopping) but I managed to reflash the bin with the linksys utility by using the port #4 (dunno why but it didnt work on any other port) on the router. It work now, maybe that could help some people.
xtacydima
DD-WRT User


Joined: 30 May 2008
Posts: 66

PostPosted: Mon Mar 28, 2011 5:14    Post subject: Reply with quote
I also have problem that is similar, I bricked mine after bad flash from dd-wrt to open-wrt and now I just get a blinking power led light an dnothing more. I want to get dd-wrt back on.

I got the skynet tftp software and I have all wrt350n builds from mini to standard.

What is my best thing to try here?
Peabody
DD-WRT Guru


Joined: 28 Dec 2009
Posts: 1518

PostPosted: Mon Mar 28, 2011 11:59    Post subject: Reply with quote
xtacydima wrote:


What is my best thing to try here?


Reading the forum announcements. Esp. peacock 6.

_________________
I fix "shortcuts". If you don't have time to read thoroughly, I don't have time to re-type what you missed.
xtacydima
DD-WRT User


Joined: 30 May 2008
Posts: 66

PostPosted: Mon Mar 28, 2011 14:34    Post subject: Reply with quote
@Peabody

OK, I followed those steps and have some success, but weird things are happening.

I was able to successfully load the mini image of the 350n through tftp (run as admin option in win7, firewall & AntiVirus were off) and I waited 5 entire minutes as suggested. I did a proper reset twice (waited 4min)

My Power LED light no longer blinks permanently, after bootup it is a solid Green as opposed to a forever blinking green.

I still get no IP address and if I set manually to 192.168.1.10 I get "Destination Host Unreachable" message

I also noticed when plugging in the Cat5 cable the lights are all off on LED's by 1 space

If I plug it into port 1 I get Internet ativity light, plug into port 2 and port 1 lights up, and plug it into port 3 and led for port 2 lights up... etc...

No webgui obviously... I do not think it is completely bricked now but I am unable to achieve a full recovery... what can I try any suggestions?

[edit]
adding extra info
here is a ping out from a clan start of router

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.1: bytes=32 time=536ms TTL=100
Reply from 192.168.1.1: bytes=32 time<1ms TTL=100
Reply from 192.168.1.1: bytes=32 time<1ms TTL=100
Reply from 192.168.1.1: bytes=32 time<1ms TTL=100
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.

Ping statistics for 192.168.1.1:
Packets: Sent = 37, Received = 28, Lost = 9 (24% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 536ms, Average = 134ms
Peabody
DD-WRT Guru


Joined: 28 Dec 2009
Posts: 1518

PostPosted: Mon Mar 28, 2011 17:58    Post subject: Reply with quote
Peabody wrote:
Reading ALL the forum announcements.


Those ttl=100 responses are when you have to tftp the proper firmware. I would start with oem linksys firmware. Read ALL the announcements carefully. This is explained in them already. Note 11 of the peacock will give you guidance in tftp, but you really need to read them all.

_________________
I fix "shortcuts". If you don't have time to read thoroughly, I don't have time to re-type what you missed.
Goto page Previous  1, 2, 3  Next Display posts from previous:    Page 2 of 3
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