[Q] Wifi "Error" - Rooted - Default ROM - Worked for months - sudden "error" for wifi
Crazy thing happened. I rooted my phone, still using default rom, ran for months, and NOW I get wifi "error"
When I go to the settings menu and try to connect to wifi, listed below "Wi-Fi" in the checkbox area is "Error"
Working fine for MONTHS...now, wifi broken. This happened in the past 24 hours with no changes on my part. I haven't even installed any apps through the store.
The wifi network I am on is protected with WPA, and I trust that my roommate can't hack my phone ;-)
So unless someone broke into my network, I can only assume that Verizon changed my phone or that it just broke magically.
Anyone else having this problem?
I'll look in to this error, manually, but I just wanted to put this out there in case the WAS some firmware change that broken things for people in the past 24 hours or if this is a somewhat common problem, get some feed back.
I have searched and I have not seen such an error happen without some direct cause such as rooting, changing roms, or running debloat applications, which I have NOOOOOOT done in the past 24 hours, nay, past MONTH.
Crazy thing happened. I rooted my phone, still using default rom, ran for months, and NOW I get wifi "error"
When I go to the settings menu and try to connect to wifi, listed below "Wi-Fi" in the checkbox area is "Error"
Working fine for MONTHS...now, wifi broken. This happened in the past 24 hours with no changes on my part. I haven't even installed any apps through the store.
The wifi network I am on is protected with WPA, and I trust that my roommate can't hack my phone ;-)
So unless someone broke into my network, I can only assume that Verizon changed my phone or that it just broke magically.
Anyone else having this problem?
I'll look in to this error, manually, but I just wanted to put this out there in case the WAS some firmware change that broken things for people in the past 24 hours or if this is a somewhat common problem, get some feed back.
I have searched and I have not seen such an error happen without some direct cause such as rooting, changing roms, or running debloat applications, which I have NOOOOOOT done in the past 24 hours, nay, past MONTH.
