[bytersweet]

Greatings all....It's been 5 years!

Five years ago, I bricked a Cisco E300 V1 router and could never "clear the brick" to restore it....I put it in a bag, on the shelf, and it sat there.

What had happened 5 years ago, I flashed router successfully (DDWRT), then, dropped another flash on top of that (an upgrade(?)...Router re-booted and simply hung there for 30+ minutes or longer.


I have:
1)....a JTAG cable,

2)....cat 5 cable,

3)....Putty program,

4)....FTPT2 program,

5)....soldered wires to pc lands at edge of board (no shorts and good connections),

6)....Have ORIGINAL E3000 firmware,

7)....Have DDWRT flash firmware.

....Have Putty software,

9)....Have TFTP2 software

Now I have,
1)....a flashing power light.
2)....cannot ping via cmnd and cat 5 cable to router lan port(s)


First I need to know, how I can clear all the "ram/program" out
of this and start over.

ANY step by step assistance is appreciated and, thanking all in advance!

[kernel-panic69]

First try "management mode" to flash back to stock.

https://www.linksys.com/us/support-article?articleNum=140001

If that doesn't work, serial recovery is your other option. You shouldn't need to JTAG this device unless the CFE got b0rked. There is a way to get it to flash via serial without the normal commands, see "LOM on the E3000" in the wiki.

https://forum.dd-wrt.com/wiki/index.php/Serial_Recovery

[bytersweet]

Thanks for the response!

First try "management mode" to flash back to stock.
https://www.linksys.com/us/support-article?articleNum=140001
**WILL DO!

If that doesn't work, serial recovery -
*8IS THAT USING A CAT 5 CABLE OR WHAT?

- is your other option. You shouldn't need to JTAG this device unless the CFE got b0rked.
**BEATS ME!...EVERY TIME I LOOK AT IT, I SWEAT, BP GOES UP, HEART RATE RISES.

There is a way to get it to flash via serial without the normal commands, see "LOM on the E3000" in the wiki.
https://forum.dd-wrt.com/wiki/index.php/Serial_Recovery

**WILL DO AND WILL ADVISE!

[bytersweet]

Tried "management mode"....No good...expected to see the interface of the router after 192.168.1.1 but, "nada"..I even used all the lan ports in the router and 2 different net cards that are installed.

[kernel-panic69]

Did you set a static IP to your client device @ 192.168.1.x (e.g. 192.168.1.10)? And are you sure your browser isn't in https-only mode? I generally use a much older version of FF ESR portable for older devices like this for management mode / emergency room / miniCFE webserver.

[bytersweet]

Did you set a static IP to your client device @ 192.168.1.x (e.g. 192.168.1.10)?
**Each and every time I attempted a fix.

And are you sure your browser isn't in https-only mode?
**I was just going to mention that!...I type in the 192--- and the address line defaults to https...Using Firefox here and windows 7.

I generally use a much older version of FF ESR portable for older devices like this for management mode / emergency room / miniCFE webserver.

**I have 2 nic cards, 1 add-on, 1 on-board...I click on each and tray to hit "status" but, both are greyed out...BOTH WORK as tested to get net access.

[kernel-panic69]

You have to either use http or turn that feature off in Firefox; or use a much older version. Sounds like your network cards have an IRQ conflict or something. Are they disabled by Windows or is the one onboard disabled by the BIOS on the motherboard, or...

[bytersweet]

You have to either use http or turn that feature off in Firefox;
**I looked around and believe it is OFF although after I enter 192--- it reverts back to https....I saw in FF where it said NOT to use https and hit it to shut down...

or use a much older version.
**?????

Sounds like your network cards have an IRQ conflict or something.
**I have no idea as both of them work fine accessing the net but, like stated, "status" is grayed out
Are they disabled by Windows or is the one on-board disabled by the BIOS on the motherboard, or...

**What bugs me is that everything works (nic)...In the morning, I will probably remove 1 car just to see what happens..

[kernel-panic69]

I guess manually entering http://192.168.1.1 is too easy...

[bytersweet]

[b]HUH????????!!![/b]

I have been entering that all along in fact, my fingers are on "automatic pilot" entering that into address bar!

I have an older laptop that I may be able to utilize and will try it early afternoon-ish (11-12-2k21)

[bytersweet]

PS....In attempting to make "contact" through cat 5 cable with router, i "took turns" disabling net cards...this time I will remove the "add-on" card, not that it should make a difference.

[bytersweet]

I fired up a windows xp laptop...set the adapter to 192.168.1.55....Opened a cmd window and typed;

ping 192.168.1 and it said destination host unreachable, packets: sent 4 , received 0 , lost 4 (100% loss.

Did same for ".55"...Further, the window went on to indicate "media state - media disconnected".

[kernel-panic69]

Are you sure the cable is good? Did you try disabling and re-enabling the network interface in XP? This shouldn't be that difficult to do. You should be able to use either management mode or tftp to recover this device. Serial recovery requires both a working ethernet connection and the use of a USB-UART-TTL adapter. Have you tried connecting wirelessly? There isn't a LAN port issue noted on this device.

https://forum.dd-wrt.com/wiki/index.php/Linksys_E3000

Please don't get lost in that wiki on initial flash; 21676 / K3X is probably the "safest" starting point, if you are using an older Firefox ESR portable browser, Pale Moon Portable, or IE.

Are you sure you are entering http:// first? And you have to ping 192.168.1.1 ... either you have typos in your posts or you are falling short somewhere, I don't know which.

[bytersweet]

Are you sure the cable is good?
**absolutely positive..have used 3 cables all with same result.

Did you try disabling and re-enabling the network interface in XP?
**yes, I did.

This shouldn't be that difficult to do.
**that is what I thought 5 years ago and now it comes back to bit me in the a$$ again.

You should be able to use either management mode or tftp to recover this device.
**I tried - no luck.

Serial recovery requires both a working ethernet connection
**which I have-

and the use of a USB-UART-TTL adapter.
**I have been using a cat 5 cable from computer(s) net cards to lan port(s) on the e3000 router.

Have you tried connecting wirelessly?
**I cannot see how that could work since I cannot "contact", ping, etc etc or see any indication of contact with the router nor see any user interface for the router or management mode.

There isn't a LAN port issue noted on this device.
**not sure what you mean by this.

https://forum.dd-wrt.com/wiki/index.php/Linksys_E3000

Please don't get lost in that wiki on initial flash; 21676 / K3X is probably the "safest" starting point, if you are using an older Firefox ESR portable browser, Pale Moon Portable, or IE.

Are you sure you are entering http:// first?
**I have entered the 192 etc etc etc, and all entries were verified each and every time.....

And you have to ping 192.168.1.1 ...
**I have done that too many times to count!...Have also played with the last 2 #'s

either you have typos in your posts or you are falling short somewhere, I don't know which.
**I can believe "typos" with my postings but, NONE in any entries in my hardware.
NOTHING appears to be able to get into the router...From what I read, it appears that the boot loader screwed up in some way but, unless I can "wipe the router" and get into it, it would only appear that jtag would be next...I have the wires already soldered in place from 5 years ago and a cable.

[kernel-panic69]