It didn't work. No GUI after restart. Only two 100 ping response when I power cycle. All lights blink once and then remain off, as a normal boot. All Ethernet ports looks good, blinking as traffic when connected.
I've read the recovery part from here https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=51486 SECTION 6
I've tried flashing OEM Linksys .bin and the 21676_NEWD-2_K2.6_mini-e900.bin recommended in the wiki.
Flashing is always successful and then remains pinging well with a TTL of 100. But when I complete the following steps It fails. No GUI and no ping response apart from the first two 100 TTL.
It looks like it's not totally bricked, but there's something in the flashing procedure that's not completing well.
Flashing steps tried include the WIKI, the TFTP https://wiki.dd-wrt.com/wiki/index.php/TFTP_Flash.
I've seen differences in the steps following the flash, in the order of hard resets and power cycles for example, so even I've read a lot I'm not sure which procedure is the right one for my situation.
I'll appreciate If anyone can help.
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Tue Jun 02, 2020 1:21 Post subject:
Trailed mini build is only for initial flash. Not sure if newer K2.6 trailed mini builds are messed up or not. Upgrading is a process that must be done in steps in the correct order using the generic nv64k builds, otherwise. Also, you will want to ensure your LAN ports are working after flashing per the wiki.
If you are using any Chromium-based router, then you will run into issues. This is a well-known problem. Some people recommend that if you do use Chromium-based browsers, to use incognito mode with NO extensions loaded and your antivirus and firewall off... without the router connected to anything but your PC via wired LAN port. _________________ "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
Yes I've used a Chromium based browser for the initial flash.
I've tried many combinations of procedures for TFTP flashing, including OEM and DDWRT E900 mini firmwares, Windows CLI TFTP and Linsys TFTP. Also tried combinations of after successful flashing steps (hard reset, power cycle, etc) according to wikis posted here and also the ones in the official Linksys web site.
I'm stuck in the point where I only get twon 100 TTL pings after a power cycle.
Is there anything else to do before going for wired unbricking techniques?
Thank you
Joined: 14 Sep 2019 Posts: 301 Location: Maine, USA
Posted: Tue Jun 02, 2020 19:04 Post subject:
ohnoo wrote:
Yes I've used a Chromium based browser for the initial flash.
I've tried many combinations of procedures for TFTP flashing, including OEM and DDWRT E900 mini firmwares, Windows CLI TFTP and Linsys TFTP. Also tried combinations of after successful flashing steps (hard reset, power cycle, etc) according to wikis posted here and also the ones in the official Linksys web site.
I'm stuck in the point where I only get twon 100 TTL pings after a power cycle.
Is there anything else to do before going for wired unbricking techniques?
Thank you
To be clear, you're manually starting the tftp transfer at the same time the two pings are reported. The tftp transfer appears to complete. During the tftp transfer, the pings should continue past the initial two pings. Is this all correct?
If so, you're probably having the same issue as this thread (different router model) and you'll have to initiate the tftp from the command line via a serial connection.
Yes I've used a Chromium based browser for the initial flash.
I've tried many combinations of procedures for TFTP flashing, including OEM and DDWRT E900 mini firmwares, Windows CLI TFTP and Linsys TFTP. Also tried combinations of after successful flashing steps (hard reset, power cycle, etc) according to wikis posted here and also the ones in the official Linksys web site.
I'm stuck in the point where I only get twon 100 TTL pings after a power cycle.
Is there anything else to do before going for wired unbricking techniques?
Thank you
To be clear, you're manually starting the tftp transfer at the same time the two pings are reported. The tftp transfer appears to complete. During the tftp transfer, the pings should continue past the initial two pings. Is this all correct?
If so, you're probably having the same issue as this thread (different router model) and you'll have to initiate the tftp from the command line via a serial connection.
You understood perfectly. I've checked the post. Symptoms are the same. I'll search for serial recovery information for my E900, buy a cable and try to follow directions.
Still open to other options.
Thank you.
### Change it to 0x2080842 (2) ###
CMD: [ifconfig eth0 -addr=192.168.1.1 -mask=255.255.255.0]
Device eth0: hwaddr C8-B3-73-13-8F-8F, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
Automatic startup canceled via Ctrl-C / ESC
CFE> ▒n▒w▒|▒m▒▒▒▒{|߿▒e
That's the garbage when I type.
So I tried with tftp, putting the factory .bin firmware. This time, while TFTP shows successful transfer, Serial window shows booting process and then I get CFE prompt, but again when I try to type commands, same garbage is shown.
I'm using Windows 10 64b, Putty for 64b, No antivirus, TFTP2 application. CP2101 USB to TTL adapter, Windows P&P driver.
I've tried tweaking the windows serial port buffering with no luck.
Thank you very much, but it doesn't work. Same result.
The USB adaptor has a red led light, almost always on. I've seen that one turn off and another blue one blink occasionally. But the red one is the most persistent. Don't know what they are telling.
I've read the post suggested, tried with Kermit, but had problems settin baud to 115000, it reverts to 49464.
I've tried three USB ports.
Any ideas?
Tried to share this in that other post that's more specific but it's locked.
Thanks!
Then you have a bad connection to the router mainboard. Probably the ground.
You where precisely right!!
My gnd solder was loose, so I've reinforce all connectors.
I've broke CFe at first attempt, then followed Serial recovery instructions, 1-erased nvram, 2-issued proper flash command, 3- put latest factory firmware with CLI TFTP, 4- go command, and the following instructions.
About lights? well, according to what happened when worked well the red one means power on, and the blue one means serial traffic. I've only used TX,RX (crossed cabled with router board) and GND, properly soldered
I really want to thank all the support offered. I'll start to study all this further and see If I can give it back eventually.
Edit: Successfully flashed DD-WRT v3.0-r42557 mega