1) flashed with "dd-wrt.v24-14896_NEWD-2_K2.6_mini_wrt610nv2.bin" and then once that came up I flashed again with "dd-wrt.v24-14896_NEWD-2_K2.6_big.bin".
Everything seemed to go pretty smoothly. I continued down the steps and used ultraedit to edit "cfe_e3k-GENERIC-DL.bin" with my routers settings. I got the file transferred and ran the ssh commands to write the cfe file.
-------- End Pre - Information -------
Here's where the problem begins:
I went back to the instructions and screwed up! next steps says "Go back to the router’s web interface and upload the modified firmware, making sure your set the “Reset to defaults” option." well I went back to web and restored to defaults before uploading the modified firmware.
I've tried all the basic reset style recovery methods, including 30-30-30.
I've tried pin 8-9 short
I don't have a cable I can use to try the serial method.
Power light just keeps blinking. I get absolutely nothing from the ethernet ports (no power?). I can ping -t all day long and I don't get a single packet through. As such I can't telnet, ssh, tftp etc. Am I screwed unless I get a serial cable?
Joined: 26 Jan 2008 Posts: 13049 Location: Behind The Reset Button
Posted: Tue Jan 24, 2012 14:12 Post subject: Re: am I just beyond the usual brick?
elmo2274 wrote:
Power light just keeps blinking. I get absolutely nothing from the ethernet ports (no power?). I can ping -t all day long and I don't get a single packet through. As such I can't telnet, ssh, tftp etc. Am I screwed unless I get a serial cable?
Pretty much.. I have not figured out why but sometimes (50%), these routers need jtag to clear nvram or serial does not work.. no output.
You might be able to tell.. I need to confirm but I think if the lan lights do not initialize at power up, (meaning, they should all illuminate for a short time), the router will need jtag to clear nvram.
jtag is not so easy on this router. You must 1st enable the circuit by bridging some pads. There is a pic in the convert thread.
Try serial.. if no output, then you need jtag. Maybe send it to someone to fix.
Am in the process of trying to fix a bricked e3300 linksys router. Have soldered the serial connection and can access CFE.
Sometimes I get a successful upload other times an IO failure ( see below ). It seems like the router stays alive for 5-10 seconds and then goes to "flashing power led mode" and then I can no-longer enter commands to the CFE.
All help appreciated.
Corncrake
Code:
CFE version 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: Mon Nov 8 16:22:24 CST 2010 (lzh@team2-complier)
Copyright (C) 2000-2008 Broadcom Corporation.
Init Arena
Init Devs.
No DPN
This is a Parallel Flash
Boot partition size = 262144(0x40000)
et0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.10.56.51
CPU type 0x19740: 480MHz
Tot mem: 65536 KBytes
mac_init(): Find mac [C0:C1:C0:9F:32:95] in location 0
Nothing...
country_init(): Find country code in location 0
The country is same
Device eth0: hwaddr C0-C1-C0-9F-32-95, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
Automatic startup canceled via Ctrl-C
CFE> ^C
CFE> flash -ctheader : flash1.trx
Reading :: CODE Pattern is CORRECT!
upgrade_ver[v1.0.4] upgrade_ver[10004] 4712_ver[0]
Failed.: I/O error
*** command status = -4
CFE>
Just like to say think you to every one contributed to the thread. I have unlocked my bricked Cisco E3000 with all information I got here.
I accidently loaded wrong version of openwrt and bricked E3000. Tried two windows ping, tftp method. didn't work because tftp failed at middle for transfer, tried with ddwrt mini file, file sent in successfully but still not worked. Also tried 8,9 pin short method that doesn't work either. (I used a small flat screw driver to open the box. saved me the cost of Trox 10 security driver). Here is how I debrick the E3000. I really think I got it by luck. and hope the information might help somebody.
1. start ping -t 192.168.1.1 and let it run.
2. short 8,9 pin and then turn on E3000 power and continue short 8,9 ping for 5 sec.
3. use browser to hit 192.168.1.1 and got no result.
4. some reason I saw the ping window start response.
5. use tftp to send in stock firmware. I happened to got typo, so got quit a few seconds delay. but the whole 7meg bytes of file sent in successfully.
6. ping still has response for a few more seconds. and then stopped.
7. 30 seconds later tried to hit http://192.168.1.1 and I got response from stock firmware.
Just like to say think you to every one contributed to the thread. I have unlocked my bricked Cisco E3000 with all information I got here.
I accidently loaded wrong version of openwrt and bricked E3000. Tried two windows ping, tftp method. didn't work because tftp failed at middle for transfer, tried with ddwrt mini file, file sent in successfully but still not worked. Also tried 8,9 pin short method that doesn't work either. (I used a small flat screw driver to open the box. saved me the cost of Trox 10 security driver). Here is how I debrick the E3000. I really think I got it by luck. and hope the information might help somebody.
1. start ping -t 192.168.1.1 and let it run.
2. short 8,9 pin and then turn on E3000 power and continue short 8,9 ping for 5 sec.
3. use browser to hit 192.168.1.1 and got no result.
4. some reason I saw the ping window start response.
5. use tftp to send in stock firmware. I happened to got typo, so got quit a few seconds delay. but the whole 7meg bytes of file sent in successfully.
6. ping still has response for a few more seconds. and then stopped.
7. 30 seconds later tried to hit http://192.168.1.1 and I got response from stock firmware.
Pin shorting is almost a BAD idea. There are much better and safer ways: Wiki: Serial Recovery _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
Joined: 02 Jan 2011 Posts: 56 Location: Ostrava, Czech Republic
Posted: Fri Feb 21, 2014 9:34 Post subject: RE
With pin 8 9 short, on the first try, E3000 debricked. I have bought serial module, cables, no success, but this simple way with shorting did the job. _________________ 1 x Asus RT-N18U
1 x Linksys E3000 DD-WRT build 23838 NEWD-2 K3.x mega
1 x Linksys E3000 DD-WRT build 23919 NEWD-2 K3.x mega
1 x Linksys E3000 DD-WRT build 25628 NEWD-2 K3.x mega
Have been at this for over a month now. E3000 V1
bricked. I had flashed ddwrt into it and after
"upgrading" that build, the 2nd flash simply hung
and did nothing which lead me to unplug the router
and thus the brick.
I have a "FTDI CHIPSET USB CABLE FT232 USB CABLE TO
TTL SERIAL ADAPTER CABLE" (and using "Putty") that i
purchased and made the correct connections but,
there is nothing appearing in the "PUTTY" window
when router turned on.
I even ordered a replacement cable just to be sure
no anomaly with the cable. I have downloaded the
seemingly correct driver for same for WINXP and I
see the virtual port and i have i have configured it
correctly. All i am seeing is the blinking power
light.
Any other avenue I can take to resuscitate
this router?..via lan?....Short pins?...I am really
shy about the "pin-short" but, it looks like my
options are being squeezed here.....I really need
some detailed assistance here.
OK... you didn't hear this from me and don't do it if not really last resort.
Unplug power, open the router, get really small screwdriver or pin, find flash chip and short pins as on picture. Keep shorted, plug power and keep it shorted for 5s, then release. Router is now in recovery mode. Plug LAN cable and open your browser to 192.168.1.1
Don't short any other pins!!!
Good luck!
This. Yes. Thank you, Eko, for your post from way back when. Using this method (shorting pins 16 & 17), I was FINALLY able to access the recovery web interface and upload dd-wrt.v24-33555_NEWD-2_K2.6_mini_wrt610nv2.bin which is now running (seemingly) happily on my WRT610N v1.
and don't do it if not really last resort.