Ok; as a disclaimer, I am a long-time Rooter. For the record, I have not rooted since I had my Note 3; since then I have had a Note 4 and now an S7 Edge. This Sunday, after I had taken Sprint's newest security release (Sprint = PF2) I noticed that my WiFi would not enable. If you enabled it, it would say it was connecting, but then it would just switch back off. I started to dig into what was going on. I then rebooted into recovery...only to see that my binary was CUSTOM....Knox was/is not tripped. I then restart the phone to find in settings that my phone is no longer listed as official, it is now CUSTOM. Now I irritatedly factory reset my phone from settings. All is now clean and OFFICIAL. I try to enable Wifi, nope, it will not turn on. I then restart into recovery to find my device is now CUSTOM again....Rinse and repeat. I then do a factory reset from recovery...same failed result after a restart of the phone. Sprint failed to resolve (I have a replacement coming) and the Samsung REP at Best Buy was flabbergasted. The Samsung REP worked his magic only to realize that his magic did not resolve the issue either. I do not have HummingBad; scans have proven negative, in addition to a factory restart resolving that virus (even if I had it).
Now I find out that a friend of mine's--Sister-in-Law has an S7 with T-Mobile having the same CUSTOM Rom issue; although she is not having the WiFi issue.
This has got to do with the phone/version of Android.
What are everyone's thoughts?
Thank you for reading;
Nick
Now I find out that a friend of mine's--Sister-in-Law has an S7 with T-Mobile having the same CUSTOM Rom issue; although she is not having the WiFi issue.
This has got to do with the phone/version of Android.
What are everyone's thoughts?
Thank you for reading;
Nick
from xda-developers http://ift.tt/29jZtSi
via IFTTT
No comments:
Post a Comment