Page 1 of 1

Strange router problem with Cricket

Posted: Mon Aug 17, 2020 7:23 pm
by wdwilson99
I have now locked up (bricked) two different routers, both with the EC25AF modem in them. Both were based on OpenWrt but had customized it. I know how to do the Uboot procedure, holding in the reset button, plugging in the power, watching LED flashes or counting to 20 and connecting over the LAN port with a windows PC to 192.168.1.1. I tested that procedure and got the firmware upload screen. Then I plugged in a cricket data only SIM.

With both routers I was able to get a connection, I could surf the web, read my email, watch Netflix, run speedtests, etc. With both routers, after about an hour and 200-500 MB of data , I was suddenly disconnected from the internet and the LAN port would no longer respond. I powered off. I powered off, did a reset. I powered off and did a debrick/UBoot procedure. Nothing, no response on the LAN port. The lights look normal, but the LAN ports are not responding. I did make one mistake twice, I turned off the WIFI modems because I never intended to use the WIFI, so I can't try that and see if it too is unresponsive.

The first router was a KuWfi and after their tech support had no solutions, I sent it back to Amazon. The second router is a GL.Inet X750. I just emailed them a detailed description of what happened and the various ways I have tried to resurrect the router. But, I suspect that this one too is bricked. It's very strange. Two different hardware builds, but the same type modem.

I have never seen anything like this is my 50 years of electronics, I can still build a PC from parts and have recently built two Raspberry PI systems, so I am not a complete idiot with hardware and software.

Re: Strange router problem with Cricket

Posted: Sun Aug 23, 2020 12:05 pm
by Didneywhorl
I'm sure you did this but, did you set your PCs network device to a static IP and then scan the network for all connected devices to see if its there and what IP the router has given itself?

You might just be out of the subnet.