![verizon actiontec mi424wr rev 1 firmware 52.0.7 verizon actiontec mi424wr rev 1 firmware 52.0.7](https://i.ebayimg.com/images/g/UHsAAOSwSQ1gMu7O/s-l300.jpg)
- Verizon actiontec mi424wr rev 1 firmware 52.0.7 install#
- Verizon actiontec mi424wr rev 1 firmware 52.0.7 serial#
The tech was able to flash the router with the 56.0.10.7 firmware and configure up the static ip without issue, so this was not the problem. So I can say, that this bricked failure mode definitely has something to do with a non-standard/custom configuration. He un-boxed, and did the usual setup with the new router. I drew up some network diagrams (which the tech barely understood) and after about 20 mins of discussions, convinced him to enable the ethernet port on the ONT. Since i spent the entire morning waiting on a tech that wasn't going to show up, i decided that, like many, to ditch the Actiontec for my critical systems.
![verizon actiontec mi424wr rev 1 firmware 52.0.7 verizon actiontec mi424wr rev 1 firmware 52.0.7](https://images.bonanzastatic.com/afu/images/f498/e15c/cf94_5483138840/EEE230AD-B379-4100-94BC-993FE13278C5.jpeg)
Verizon actiontec mi424wr rev 1 firmware 52.0.7 install#
(!!!!) He was able to expedite it as not but an hour later the local tech guy (turns out to be the same guy that did the install 10 months ago) calls and eventually shows up. We went thru the usual diagnosis (this is the 3rd time i've had to do the standard diagnostic procedures). I spent 1.5 hours on hold to find out that the ticket filed yesterday for a dispatch got dropped on the floor and they missed the appointment. I'm really surprised that no one else has posted anything yet. I found one post by someone on the forum (perhaps you?) that had reported this issue. (according to the support lady on the phone for the 3rd time) This seems like a fairly large bug.
Verizon actiontec mi424wr rev 1 firmware 52.0.7 serial#
(does anyone know where to find the serial pins? is it 3.3 volt or 5 volt serial?)Īnyway, I know they said they pushed out some kind of firmware upgrade for FiosTV related fixes. If only i could get a serial console on it, I could probably figure out what's going brain dead. and the default config is for DHCP on the MoCA side, which is not present when you have a static IP business account. My spidy sense tells me they added some kind of auto reboot feature in the latest firmware, that if the actiontec doesn't have a pingable route to some special verizon IP address, it reboots itself. I want to see it running with a Static IP, latest firmware without any of my vlan configurations, without issue. When (or IF) they show up today, the first thing he will be doing after configuring the static IP address on the MoCA side, is calling his support agent and have them do a firmware push. Tomorrow, the tech will wait until the actiontec is reconfigured and the network is fully up this time. An end user should not be able to brick a router with simply configuration. If it's not a misconfiguration on the NID side of the Verizon network, seems like a firmware bug to me. Tech is coming out tomorrow with a new modem, but thought I'd ask anyway. I am using some of the advanced features of the Actiontec for my network, which, I'm betting Verizon hasn't tested well in their dev lab. Has anyone else seen this, and perhaps have a workable solution? The new one is a Rev C, the old one was a Rev A or B, so seems to be hardware independent. So this is what i did, and now does exactly same behavior as the old Actiontec.
![verizon actiontec mi424wr rev 1 firmware 52.0.7 verizon actiontec mi424wr rev 1 firmware 52.0.7](https://i.ebayimg.com/images/g/g-gAAOSwZKJb8dOD/s-l640.jpg)
(4.0.16.1.45.160) So, after doing some googling, others were suggesting upgrading to the latest firmware. The tech decided to just throw a new modem at it, and he was (barely) able to get it back up with a new box.Īfter the tech left, I started configuring the actiontec config for my static IPs again, and during the configuration, SNAT (static nat) functionality seemed to be broken with the shipped firmware. (I'm guessing they must have pushed new firmware to those in my area?) Fios phone support were mystified, send out a tech. This spontaneously started doing this early in the AM. When in "amber light mode," It is pingable on the 192.168.1.1 from the back LAN ports, but telnet, web, etc. Holding reset (at the right times during the above sequence) will turn the power light amber, for which it then sits forever and does nothing. power light goes dark, and starts the cycle all over again power light blinks for another 4 seconds power light goes off for about 5 seconds Symptoms are, on power up, green light flashes for about 6 seconds Seems that the latest firmware (4.0.16.1.56.0.10.7) bricked my Actiontec router.