Looks like the AU (Australia) version of the EA8500 with the latest stock FW is not able to be flashed.
I received my CP2102 chip based USB/TTL cable today, but was unable to flash router.
Using the http://mrjcd.com/EA8500_DD-WRT/ instructions, Putty was not able to stop the boot sequence and get to the (IPQ) # prompt.
Turning router on and hitting a key does delay the bootup as it counts 2...1...0 but it cannot be stopped.
Same thing happened with a PL2303HX cable last month, on 3 different computers.
I have triple checked all steps.
The EA8500 is now back as an AP on stock FW... _________________ ------------------------------------
Linksys EA8500 DD-WRT r45891 (Gateway)
Linksys WRT1900ACv1 DD-WRT r45891 (AP)
Netgear/Telstra V7610 (spare AP)
Billion BiPAC 7800NXL (spare AP)
Netgear WNDR3700v4 DD-WRT r44772 (spare Gateway)
Photos: https://www.flickr.com/photos/nickant44/albums
If possible, verify that your usb/ttl cable works by trying it with another router. Could also be the serial port itself.
I have an ea6300v1 that stopped responding or even outputting serial info at all.
Without doing anything to the connection between flashes. _________________ I am far from a guru, I'm barely a novice.
Joined: 21 Jan 2017 Posts: 1677 Location: Illinois Moderator
Posted: Thu May 17, 2018 14:19 Post subject:
Wolf Kodi wrote:
Firmware: DD-WRT v3.0-r35900M kongat (05/08/1
Is Web GUI config backup broken for anyone else?
I was able to enter into the page just fine and save a backup ok. I didn't try to restore any settings.
What are you trying to do, restore a backup?
If so, what build version did you save on?
I suspect your issues is that at Rev.35700 the nvram size changed and bonked any older b/u settings on our EA8500. The new nvram size is 128k vs 64k.
I had to completely reset the saved settings when I went from 35030 to 35700. from 35700 to 35900 no reset was necessary. I suspect the mappings changed and thus a reset is absolutely necessary....a PITA for sure if you had a lot of custom settings....
I was able to enter into the page just fine and save a backup ok. I didn't try to restore any settings.
What are you trying to do, restore a backup?
If so, what build version did you save on?
I suspect your issues is that at Rev.35700 the nvram size changed and bonked any older b/u settings on our EA8500. The new nvram size is 128k vs 64k.
I had to completely reset the saved settings when I went from 35030 to 35700. from 35700 to 35900 no reset was necessary. I suspect the mappings changed and thus a reset is absolutely necessary....a PITA for sure if you had a lot of custom settings....
No, I'm not trying to restore a backup. I made some changing and want to create a backup.
Posted: Thu May 24, 2018 11:48 Post subject: Still have Linksys FW
I have Linksys EA8500 (US version). I did everything like describe http://mrjcd.com/EA8500_DD-WRT/ (but I has match more #####) and all messages from the router was the same. But after command reset the router starts with original Linksys FW 1.1.5.178908. I repeated it with latest factory-to-ddwrt.img but nothing changes.
Posted: Thu May 24, 2018 14:31 Post subject: Re: Still have Linksys FW
Vadim_ka wrote:
I have Linksys EA8500 (US version). I did everything like describe http://mrjcd.com/EA8500_DD-WRT/ (but I has match more #####) and all messages from the router was the same. But after command reset the router starts with original Linksys FW 1.1.5.178908. I repeated it with latest factory-to-ddwrt.img but nothing changes.
After I clicked to Restore previous firmware from Troubleshooting/Diagnostics menu the router freezed. And after power off/on it starts with DD-WRT.
Posted: Thu May 24, 2018 14:39 Post subject: Re: Still have Linksys FW
Vadim_ka wrote:
Vadim_ka wrote:
I have Linksys EA8500 (US version). I did everything like describe http://mrjcd.com/EA8500_DD-WRT/ (but I has match more #####) and all messages from the router was the same. But after command reset the router starts with original Linksys FW 1.1.5.178908. I repeated it with latest factory-to-ddwrt.img but nothing changes.
After I clicked to Restore previous firmware from Troubleshooting/Diagnostics menu the router freezed. And after power off/on it starts with DD-WRT.
You must not have flashed both parts to begin with.
Be sure to flash a .bin firmwre. Kong or BS newest is ok.
good luck
Joined: 21 Jan 2017 Posts: 1677 Location: Illinois Moderator
Posted: Fri Jun 08, 2018 16:12 Post subject:
Since there hasn't been a post here in a while I thought I would chime in with the "Best Build."
As of right now 6-8-18, as far as I am concerned, the last good build from Kong was 35030V2 from Feb 20th 2018 . Scroll back a few pages to find my link to the build. MRJCD hasn't put the file I sent him on his archive site yet.
As far as BS builds go, 33555 from Oct 2017 or 33772 from November. There was a reason why I didn't like 33986; I think it was QOS was getting wonky on wired LAN.
The latest 36100 Kong has bunked mDNS due to bad DNSMASQ code and so iOS and apple devices have issues with dropping connections and not being able to see each other. This also affects anything using the Bonjour protocol.
Linksys EA8500
DD-WRT v3.0-r35030M kongat [02/19/18]
Linux 3.18.95-rc1 #281 SMP PREEMPT Mon Feb 19 22:32:49 CET 2018
from my notes using r35030M:
If reboot router you will have to 'APPLY SETTINGS' in services page after time is syc before DNSCrypt will work --- or disable DNSCrypt and reneable it.
also noted:
EA8500 switch + USB SAMBA + ovpn server tryied installing r35030M over r36080M caused a reset to factory....I done this twice.
It will install ok over an older build.
I have every EA8500 Kong firmware since 09/18/16 but I only post on the site ones that I think are deserving.
I put up the r35030M because you ask
Joined: 03 Jan 2010 Posts: 7429 Location: YWG, Canada
Posted: Sat Jun 09, 2018 10:39 Post subject:
lexridge wrote:
Is kong still actively developing for the 8500, or is it a dead horse?
kong does more than brainslayer does. at least kong listens to us, aka k4.x shit qos etc, he just probably doesn't know the exact issue yet. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Posted: Mon Jun 25, 2018 4:01 Post subject: I realize this may be a tangent that should create a fork...
However I have a question for the developers (or the others in the know...), How big a deal would it be to create a variant of this build for the EA6350v3 which happens to be a qualcomm chip (V1 and V2 were broadcom)?
