I don’t have an answer to your question, but maybe our good friends might know of a location for ancient but less ancient firmware files.
It might just be worth trying the ‘post-bad flash’ emergency recovery procedure, which is as follows:
—
• Set your machine to 192.168.1.11 / 255.255.255.0 / gateway 192.168.1.1
• Plug ethernet cable into modem’s port 2 or 3 and into your main switch
• Power the modem off
• insert a pokey implement into the modem’s reset hole to depress the switch (NB there is a similarly sized but
protruding WPS button)
• Power modem on, keeping poker poked in all the time still
• Keeping poker in, LED will flash for 25s then go solid red
• Release poker
• If the device is left in the solid red light mode then a recovery webpage should become visible at
http://192.168.1.1, but only if the ethernet cable is connected to port 2 or 3. Port 1 or is it 4 -which is it ?-will not work, depending on which way you read the port numbering. (I think the port on the far right is the bad one.)
• in the modem’s web page’s file selector prompt, select the firmware file
<something>.bin • After you hit [enter] at the load firmware prompt, after so many secs the screen should change to show a [back] button. (If not, then you may have put the ethernet cable in the wrong port, so check it is in port 2 or 3)
• Takes forever to blow flash, no UI feedback
• after ~2 minutes the modem will reboot (no progress indication)
• When the modem web UI comes up, at
http://192.168.1.1, log in with username=admin, password=1234 (or username=supervisor, password=zyad1234 )
• Forced password change, set password to your choice
All done.
—
—
Config file loading: If you are then loading your own saved XML config file:
• using the usual web UI menu option "configuration" > "restore", choose an XML config file
• When you have waited for a minute or so, hit refresh in the web browser
• you have to make sure that you
go back into the the "configuration" menu again, then the modem will reboot
• The modem’s IPv4 address will possibly now change - it might now be different when the modem boots if the config file specifies an IP address that is something other than the default, so change your machine’s address accordingly if necessary
• Wait an age until the modem config is loaded (v. approx
4 mins (!) for me)
Then config loading has completed.
—
I use this procedure to flash all of my B10A modems with kitizen johnson firmware. I have very many. I added the note about loading saved config files because the web UI code that handles this procedure seems to be very strange indeed, or let’s just be less generous and say that it’s simply ‘bugfull’.