Posted: Sun Jul 24, 2016 5:55 Post subject: Compile smallest firmware for E3000
Hello,
I need help for building my own DD-WRT firmware of E3000. The router is bricked, I tried the following:
1. Ping 192.168.1.1 works for a few seconds after power on but then it times out. TFTP firmware uploading works for a few seconds and then lost connection.
2. then I connect Serial console: I cannot see any output on Putty, however, if I keep pressing CTRL+C, I am able to stop the router, ping 192.168.1.1 works continuously, but TFTP to router has no response at all.
It seems the router can accept TFTP if I do not hit CTRL+C, how ever the minimum image size I have is 3.7MB, the transmission times out at around 2~3MB.
How can I compile a image for E3000 which only contain necessary part for WEB Flashing so I can send it with tftp before the connection times out? Once this image is flashed, I can flash normal firmware to get router working.
I had also bricked my E3000 some time ago. So I can feel with you.
First I had the same behaviour when I sent pings to the E3000 after reboot. No worries.
From what opertion system on your client do you try to flash / connect to the E3000? I remember, I had some problems with windows and tried it with linux afterwards. However you should see at least some output from the serial console otherwise the connection is buggy. What parameter do you use for your serial connection?
Finally I wouldn't use any own compiled firmware. With which firmware revision have you tried it already? _________________ Ongoing experiences with:
Linksys E3000 and WRT610N v2
TP-Link Archer C9
Raspberry Pi and TP-Link TL-WR710N with OpenWRT
Posted: Mon Jul 25, 2016 17:20 Post subject: Re: Compile smallest firmware for E3000
Make sure you set these: Baud: 115200 Data bits: 8 Stop Bits: 1 Parity: none No Flow control on putty. Having done that and still nothing on putty, try to swap the RX and TX pins. I debricked my E3000 before and when the baud rate was set to 9600, I couldn't see a thing on minicom.
newnews wrote:
Hello,
I need help for building my own DD-WRT firmware of E3000. The router is bricked, I tried the following:
1. Ping 192.168.1.1 works for a few seconds after power on but then it times out. TFTP firmware uploading works for a few seconds and then lost connection.
2. then I connect Serial console: I cannot see any output on Putty, however, if I keep pressing CTRL+C, I am able to stop the router, ping 192.168.1.1 works continuously, but TFTP to router has no response at all.
It seems the router can accept TFTP if I do not hit CTRL+C, how ever the minimum image size I have is 3.7MB, the transmission times out at around 2~3MB.
How can I compile a image for E3000 which only contain necessary part for WEB Flashing so I can send it with tftp before the connection times out? Once this image is flashed, I can flash normal firmware to get router working.
In my experience with this router, even if you succeed in sending the firmware through TFTP, the router will act like you didn't. Serial connection is a more reliable option, though disassembling the router every time you need to do it is a PITA.
In my experience with this router, even if you succeed in sending the firmware through TFTP, the router will act like you didn't. Serial connection is a more reliable option, though disassembling the router every time you need to do it is a PITA.
I have been reading up other posts and it looks like serial/JTAG solutions were successfully used even when there is no ping. In some better cases, folks were able to get consistent pings after 30/30/30 or 30/5/5 reset method and that allowed them to tftp a new firmware. I looked at one guide for serial method and it does seem to be a PITA.
It's straightforward enough, especially if you can go though the WAN port, but I wouldn't risk it without the right connector. It's just too easy to short the pins and kill the serial port. That leaves opening the router, and that's what I was referring to. In any case, my point was that if you don't get enough time to comfortably transfer with TFTP, chances are, it won't work anyway even if the transfer were to finish. The CFE is just not listening. But if it works out, good for you...
