Posted: Tue Oct 27, 2020 4:47 Post subject: Trailed mini 43324 bricked my E2000, not expected right ?!
Long time lurker, thanks for all the great software through the years...
So I read the peacock thing as well as the E2000's Wiki. I had a very (don't laugh..) old version installed, 14929! This F* thing was running stable for 10 years where I had it. I wanted it upgraded for security reasons so as per the wiki and peacock information sources decided to flash with a trailed mini called:dd-wrt.v24-43324_NEWD-2_K2.6_mini-e2000
After that I would be able to use NV60k builds...
It bricked the router. I waited more than 10 minutes, which is probably totally unecessary.. Power light was still flashing after that. Did a hard reset, same result. Doesn't give an IP through DHCP and simply can't communicated with it.
Did I miss something ?
Going to have to do my 1st unbrick as where I live internet is slow, so it's not worth it to upgrade for now. I don't actually mind, it's plenty fast already...
Also, please recommend me some cable source instead of me going to eBay and buying some crappy chinese one that might not work (seen some threads where that happened...)..
Thanks to all!
There is an upgrade path somewhere on the forum it was something like:
from k2.6 mini 33215 to k2.6 mega then K3.x mega all from the same build and then you can upgrade to the latest K3.x build (which is actually K4) I am running k3.x 44628 on my E2000
Posted: Tue Oct 27, 2020 15:46 Post subject: Re: Trailed mini 43324 bricked my E2000, not expected right
Use the trailed build to TFTP, but if DD won't flash use OEM f/w. And if the nv60k builds won't upgrade, use the trailed build. This sounds familar as being an issue on some E-series routers. E.g. On k3x builds, there is no nv60k file, so trailed builds must be used either way (like on my E2500's). _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Joined: 08 May 2018 Posts: 14208 Location: Texas, USA
Posted: Tue Oct 27, 2020 16:29 Post subject:
Can't remember which 21*** build sometimes balks on upgrade, and which builds brick which E-Series, but I've discussed E-series upgrade path a few times on here... lol _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Thanks. I can't ping it so I guess TFTP is out of the question.. I also tried setting up the gateway to the same IP as the router after getting a host unreachable error..
Any ideas before ordering the serial cable please post...
Just bought one of those Nokia cables to rip apart.. Tried everything my patience let me try for hours, pinging from fixed ip addresses, pinging while / after hard reset... There's also a special one that I found that's just browsing to 192.168.1.1 while pressing reset bottom (works only on some routers but E2000 seems to have been one, dunno if it applies to newer ones...).
Still undecided if using the Wan serial port or opening and soldering. Is opening easy ? I can solder no problem...
Joined: 09 Nov 2014 Posts: 314 Location: Bakersfield, CA
Posted: Wed Oct 28, 2020 15:35 Post subject:
JdWr wrote:
Thanks. I can't ping it so I guess TFTP is out of the question.. I also tried setting up the gateway to the same IP as the router after getting a host unreachable error..
Any ideas before ordering the serial cable please post...
Thanks. I can't ping it so I guess TFTP is out of the question.. I also tried setting up the gateway to the same IP as the router after getting a host unreachable error.
Not quite following you, but as SinCalChewy alludes, have you read thru those wiki's?
You need to connect to a router LAN port with no other connections, then set a static ip of e.g. 192.168.1.10 and run a constant ping. You would only see a TTL=100 ping response from TFTP (via the CFE) a second or two after power-up. Give up after 10sec. If you still see no reply, leave it powered off for a while and retry.
Linksys (and Asus) are always more difficult to disassemble than Netgear, though not as bad as Belkin. I recall with the E-series you can use a flashlight to see the little plastic clips from the bottom vents along the edge. And/or find a youtube video. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
My E1000 had the tamper proof torx head screws
I didn't have that tool so I drilled them.
That went poorly, then I threw it away
At least you're not bitter.
@JdWr Perhaps my memory has failed me; was a long time ago I put a heatsink on my E1500 (it was be overclocked unlike the E2500's). Did a quick search on youtube; no love. So check out the E2000 FCC internal photos:
https://fccid.io/Q87-E2000/Internal-Photos/IntPho-Q87-E2000-1223244 _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Yes I did that and a bunch of other things, not reply at all. Is the reply random ? Cause I turned it on and off a whole bunch of times, sometimes during hard reset. BTW, yes it was from the wikis that I tried those things..
Mine has the torx screws too, but found out online you can use a normal screwdriver of the right size. Haven't tried yet but seems doable.
