14-03-2014 16:28 - edited 14-03-2014 16:30
14-03-2014 16:28 - edited 14-03-2014 16:30
Hi guys
Samsung s4
Have updated to kitkat OTA and now my wireless just says Connected .... Then saved secure then obtaining IP address then checking the quality of the internet connection it may then let me on the internet on wifi or it sometime just loops through them till i turn off wifi.
After i installed kitkat i went into the boot loader menu and did a reboot i have used my phone for 2 days and today I went into the boot loader menu and reformatted it again still doing the same on wifi any idea's
thanks in advance
Solved! Go to Solution.
on 14-03-2014 17:22
on 14-03-2014 17:22
@Anonymous wrote:
@Anonymous wrote:HI yes have done that, just dont seem to get any better, would have been better staying on jelly bean
thanks..
@MI5 im aware you cannot go back in firmware on iOS but I believe you can on Android ?
Maybe the OP could do as they hint on ?
You can go back but since the inroduction of "Knox" it will trip the fuse and void the warranty (until someone comes up with a fix)
on 14-03-2014 17:24
if i use odin and reinstall the latest will that trip the fuse
on 14-03-2014 17:29
on 14-03-2014 17:29
@Anonymous wrote:if i use odin and reinstall the latest will that trip the fuse
Yes, it would appear so.
The chaps are working on a fix but at the moment there are limited choices, unfortunately.
on 14-03-2014 17:31
How long have you had the phone ?
Big decision to void a warranty.
on 14-03-2014 17:36
so if i dont want to lose my warranty i cant use odin, and will have to wait till samsung bring out a patch or update hopefully...
14-03-2014 17:36 - edited 14-03-2014 17:39
on 14-03-2014 17:36
nearly a year now..
14-03-2014 17:42 - edited 14-03-2014 17:42
14-03-2014 17:42 - edited 14-03-2014 17:42
It's not clear yet if Samsung will honour any warranty on a phone with a tripped fuse, but safest is to say that you will lose it for now.
Kies cannot recover the firmware unless it was a failed flash, which it wasn't.
I'm not seeing this issue widely reported anywhere else so I'd check my advanced WiFi settings and try some different combinations of the available choices to see if it helps. Auto network switch seemed to help with the old 4.3 bug.
on 14-03-2014 17:44
on 14-03-2014 17:46
on 14-03-2014 17:46