Posted: Mon Oct 22, 2018 23:59 Post subject: Unsuccessful flashes using r37305 (10/10/18) and later
Trying to flash my ea8500 with the latest version but can only use r37139 from 10/4/18 and earlier.
New versions dont flash: message from the webgiu after 10 mins: flash failed. ssh still able to logon. console reboot or switch on/off brings the router back but not with the new version.
Also trying the kong build from 10/4 and later - same thing.
Checking with others here if you encounter the same. Is there another procedure to get these versions flashed?
There is NO problem flashing an EA8500 with either Kong or BS builds.
I suggest you maybe clear your browser cache and download the correct firmware again.
You may even have to reset the router first .....depending on what all nasty crap you may have on it.
Probably best suggestion would be use a different browser to flash thru its GUI.
I had zero problems flashing the EA8500 with any new builds released in last several months.
This is, of course, assuming it already has dd-wrt on it
--EDIT:
make for damnu sure you only use 'dd-wrt-webupgrade.bin'......don't use an .img file from main dd-wrt downloads
Last edited by mrjcd on Tue Oct 23, 2018 1:06; edited 1 time in total
Posted: Tue Oct 23, 2018 1:00 Post subject: Unsuccessful flashes using r37305 (10/10/18) and later
mrjcd wrote:
There is NO problem flashing an EA8500 with either Kong or BS builds.
I suggest you maybe clear your browser cache and download the correct firmware again.
You may even have to reset the router first .....depending on what all nasty crap you may have on it.
Probably best suggestion would be use a different browser to flash thru its GUI.
I had zero problems flashing the EA8500 with any new builds released in last several months.
This is, of course, assuming it already has dd-wrt on it
Hi MrJCD,
first let me thank you for the incredible guidance to flash an ea8500 on your website. It was fantastic to get such help!!! (Flash was done 1 year ago).
I did a hard reset 30/30/30 prior to flashing. Used chrome multiple times but didnt clear the cache and didnt use another browser. Downloaded it multiple times.
I will follow your suggestions - drove me nuts last night.
Thank you for the help and confirming that it works!
some have had trouble using new Chrome browser with winders system. I actually had once here lately when new firefox browser on the linux failed to properly update a router --- promptly switch to Chromium and it went just fine.
Could be anything ---- but there is no problem with new builds.
currently running Kong newest 10/22/18 build on the EA8500 main router ...no problems
Posted: Tue Oct 23, 2018 1:56 Post subject: Re: Same Complaint on the Flashing
reckel wrote:
Keeping partition 2 at Kong 31870M and upgrading to partition
Don't care what you may have heard that just aint a good ideal. They do silly things like that with some of the Linksys devices over in the Marvell forum.
1. Both parts use the same nvram
2. 31870M is at least a year old --- so that means that build uses 64K nvram where all EA8500 builds now use 128KB .... problem switching parts -- yea probably
If you have a favorite build you may want to keep --- then save it along with its nvram backup.
I know that if you install an old 64KB nvram build over a newly config build it will look just like the EA8500 has been reset.
Joined: 15 Feb 2010 Posts: 14 Location: Update New York (USA)
Posted: Tue Oct 23, 2018 3:23 Post subject: Re: Same Complaint on the Flashing
Okay - little level set: This is a New To Me EA8500 that I followed your very good HOW-TO at
http://mrjcd.com/EA8500_DD-WRT/ to go from Linksys crap to DD-WRT. In fact I reloaded the Linksys image, upgraded to the latest release, and THEN redid the instructions FROM SCRATCH to ensure correct process.
The result is I can get it going with the 31870M, but every any other upgrade through the GUI fails. PERIOD.
Reset or not, BS or KONG, Part 1 or 2
Looking for T/S hints as to WHY no upgrade through the 31870M GUI results in a usable image.
Willing and able to push a lot of buttons and wait out a lot of loads, but not willing to be a punching bag.
SO - given that the instructions in your page are failing, what are we doing wrong? Where is the error?
Joined: 15 Feb 2010 Posts: 14 Location: Update New York (USA)
Posted: Tue Oct 23, 2018 4:30 Post subject:
And to pass on a nugget I learned:
When doing the :
setenv image EA8500WW-factory-to-ddwrt.img
setenv ipaddr 192.168.1.200
setenv serverip 192.168.1.122
run flashimg2
there is no need to set the tftp machine to some silly static address - as shown above, serverip just has to be valid and live, the ipaddr just needs to be unassigned and on the SUBNET. (Saves futzing about with static IPs)
may be where the problem is ....
-------------
made for North America use -- others made for Euro use.
But once dd-wrt is on it should work ok anyways.
Have you tried installing a late 2017 dd-wrt version?
If made for Euro use you might use the Kong 'EA8500WW-factory-to-ddwrt.img' for first install'
I have no experience with them.....
Not sure what to tell you --- may just have some bad flash blocks in it.
You sure it has right power --- should be 12v 3.5amp.
I know mine will do wierd things when I plug a very low amp power supply to it.
AFAIK they are all made in China
That doesn't mean what country it is made for use in.
Usually depends 'where' you bought it from but if came from some fly-by-night company you really never know.
Joined: 15 Feb 2010 Posts: 14 Location: Update New York (USA)
Posted: Tue Oct 23, 2018 13:18 Post subject:
Conclusion: There is a reboot race condition at work on EA8500. May have to do with UBOOT, but not likely.
Test: last night, took a last look at IPQ printenv, got disgusted (my highball was empty ), sent a reset and turned out the lights.
Next morning - it was working on r36698!
futzing around, discovered that if reboot from the console, ONLY holding at IPQ for a minute, then doing a reset, will result in a usable system.
Both partitions are r36698 and working, but if rebooted from GUI or Console, the FW enters that network off state with error
udhcpc: read error: Network is down, reopening socket
continuously cycling.
Can't afford to keep the console port on this brick forever - and that seems to be the only way to get this to boot.
Also saw first hand the issue of upgrading with an old browser - won't do that again.
), sent a reset and turned out the lights.