Unable to enable Wifi since recent update? Knox?Knox Whos there?? - Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot

Back on stock after Cyanogen.
But for some reason... Seems like there was a system update (119MB). So I downloaded and installed it and now, it says Knox is blocking me from enabling my Wifi. I cant turn on the Wifi. Anyone else have this happen?
I have reset this device three times now and the wifi still refuses to enable.

It probably didnt update your baseband. What does your about phone say in settings?

root. delete knox. profit? try that

probably upgrade issue with baseband. See if the baseband version matches the software version, else you'd have to odin the baseband / flash full.

Related

Nexus 4 wifi troubles after upgrade to 4.4.2

Hey guys,
I am having trouble connecting to wifi after I upgraded to 4.4.2.
When I leave the house my phone shows its still connected to my home network, or if I connect to a network and return home, it shows I am still connected to that previous network. Also when I return home I am unable to connect to my home network until I reboot my phone.
Wifi optimize is off, wifi idle on sleep is off... I am not sure what else it could be. Any suggestions? I use my phone for voip over wifi (csipsimple) so this is extremely frustrating !
Thanks
Was this a OTA update? Are you running the latest radio? Did you try a factory reset?
audit13 said:
Was this a OTA update? Are you running the latest radio? Did you try a factory reset?
Click to expand...
Click to collapse
my phone was rooted, so i could not install the OTA update. I tried many ways to update it without wiping the data over the phone but it would not boot. In the end I had to wipe the phone and flash the image from the google website (manually flash, bootloader, radio, image and all). Lost all my pictures .
I used the image from : developers - google - com - Android 4.4.2 (KOT49H)
BUMP^ any ideas what I can do to fix this?
After flashing to 4.4.2, does the baseband end in .97 or .98?
audit13 said:
After flashing to 4.4.2, does the baseband end in .97 or .98?
Click to expand...
Click to collapse
I am sorry, I do not know what the baseband is

Galaxy S4 Wifi Won't Turn On

Galaxy S4 - i337m - Android 4.3
Okay, so here's my problem.
Today in the morning after I woke up, I checked my phone and it said it had downloaded a software update. It was just a complimentary update for 4.3, it said bug fixing, etc. in details. I clicked accept and the installation started.
After this, all crap started to happen.
The Wi-Fi NEVER worked again, everytime I clicked the Wi-Fi widget in the notification bar, it turned green and immediately switched back to gray. It also didn't work when trying to turn Wi-FI on from the settings menu.
I tried everything, the battery pulling, the thing of disabling the Wi-Fi energy save, and nothing worked. It all pointed to a factory reset.
So I did all my backups (My S4 was rooted), and finally made the factory reset.
After this finished, I did all the starting configuration of the S4 (like when it was brand-new). Then, I tried to turn on Wi-Fi.
Surprise, surprise. DIDN'T WORK.
I'm so desperate right now, I don't know what to do.
I'm currently downloading 4.4.2 to flash it via Odin, and see if this works.
Any help, please?
Flashing the 4.4.2 ROM you're downloading now should definitely fix the problem. I know that in some instances, us I9505 owners have to flash a stock ROM twice through Odin before the modem will function. It sounds like your software update broke the modem in this fashion, which is why the ROM install you're planning should fix it. Be aware however that installing KitKat will give you Knox if you don't already have it.
Strephon Alkhalikoi said:
Flashing the 4.4.2 ROM you're downloading now should definitely fix the problem. I know that in some instances, us I9505 owners have to flash a stock ROM twice through Odin before the modem will function. It sounds like your software update broke the modem in this fashion, which is why the ROM install you're planning should fix it. Be aware however that installing KitKat will give you Knox if you don't already have it.
Click to expand...
Click to collapse
Fine. Right at this moment I'm installing 4.4.2
Hope this works.
I'll tell you what happens.

Can't search for updates. Update Now does nothing.

Hey everyone, ever since I updated to lollipop (BOC5), my Settings>About device>Software updates>Update now button doesn't work.
When I tap on it, it doesn't do anything. Last check was on 2015-04-19, nothing since then.
I tried searching for it, but it's such a general expression, that I wasn't really successful in finding it.
Do you know how to fix this? Thanks for your help.
I'm bumping this thread because I've got no reply. Does anyone else have this problem?
[email protected]$k! said:
I'm bumping this thread because I've got no reply. Does anyone else have this problem?
Click to expand...
Click to collapse
It sounds like your device is not syncing with the update server.
Make sure that you are not rooted. Also, check if the CSC matches with your region. If it doesn't, you either need to factory reset the device and allow the device to correct it for you or flash your region's ROM. I had this problem as well after flashing lollipop from a different region.
I've updated to Lollipop via Kies, so it's the /official and correct/ ROM — that's why I'm surprised it doesn't do anything at all.
Get a stock backup and flash through odin.
Dirty flash fixed it, I didn't wipe anything but cache, and voila...it works.
Weird, but I just can't decide whether to root the phone or not since I'm really tired of ads and some other limitations (need to get rid of the s finder/quick connect buttons - the most bothersome "feature" of the phone )
Yet... on the other hand, I don't wanna void my warranty, so...
Sent from my SM-N910F using XDA Free mobile app
yes i have same issue, but my update now button is greyed out or disabled as i cant tap it, so how to enable this button and check for lollipop update???

S4 ODIN Failure com.android.phone crashes

So when this phone was on stock fng2 firmware long ago when it was current firmware. I sent it off to a guy who was offering very cheap unlock. used it fine since then. but wanted to put stock rom on it and make it completely Samsung official with no problems. so it is ready for selling. but when I get the latest firmware which is ok3 and flash with odin. after booting in those crashes start happening about 2 times per second. phone is useless. I made it to settings menu and looked at baseband and software version both show unknown so I flash stock ok3 modem still samething. then I try these full firmware images:I flash od2, same thing oh1, same thing, factory reset doesn't do a thing on the rom with issues. then I try fng2 it works perfect. then I use use od2 oh1 ok3 update.zip to get ti to latest version and it works perfect. modems upgrade and work fine. but when on latest version I reset phone from the settings menu to factory default same issue after phone as booted. so currently phone is useless if it is ever resetted. so no selling. any solutions.
the issue seems to reside with the modem. probably guy messed up a lot of settings in service mode?
You name it I have tried it most likely
any ideas anyone?
anyway to reset nvram to factory default.
i have reseted it in service mode. were it says a golden backup exists. that didnt solve anything
I've tried many many things but nothing seems to work for that issue. Only way I've gotten around it is by doing a dirty flash of kitkat with odin.

U System firmware on BLv5/6 Phone

1. Thanks to @FP_XDA and GSMZambia for the great directions found here
2. The other stuff and ideas:
The above method does put the U firmware on your phone. I had trouble getting it to connect to the network. I did try different combinations of files in the AP tar; CP; and CSC, but it would either not connect after a factory data reset or loop with the message about my SIM has changed, please restart.
I tried just flashing the following combinations through flashfire, but maybe this is a Sprint SIM issue and it works on other SIM cards; however, I have Sprint.
The U firmware seemed to work fine on the software. Including boot.img in flashfire would take away the eng_boot and root. I just had trouble connecting to the Sprint network.
Do you need to use the v5 combo file and flash a certain CP/CSC before going through the rooting steps? The U firmware CSC file is different in size, so is it a partition (PIT) issue since that will write the cache.img.ext4 file and those vary in size from stock to the U? Is there a certain order to flash in flashfire to get it to work properly?
Anyway, I downloaded several U CSC firmwares (XAA, XAS, SPR (last two are sprint)), but ran into some network issue every time. The operating system seemed stable, but the lack of connection and some random entries under settings make it so close, but yet so far.
I don't mind the Sprint firmware, but can you unlock additional LTE bands if you use the stock sprint firmware on another carrier?
Thanks for any help!
Here is more info about the Settings submenu options:
Here is some more detailed info:
The submenus under settings give me options like K twophoneservice; T roaming; Giga LTE. I think it is CSC related as those carriers are Korean based. I think this may be my issue along with a few others I've seen on reddit. Just wondering why it says that though. I used the G930U version, so not sure why this would appear.
Any help or suggestions?
Thanks
Bootloop
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.
Aggiedude said:
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.
Click to expand...
Click to collapse
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.
lvpre said:
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.
Click to expand...
Click to collapse
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
XMayhem2099 said:
7. Disable the following packages via bk or adhell
Chameleon
Sprint OMADM
Sprint OMADM Phone Interface
MDMApp
SecurityLogAgent
Security Policy Updates
Security Storage
Click to expand...
Click to collapse
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself
elesbb said:
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself
Click to expand...
Click to collapse
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.
lvpre said:
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.
Click to expand...
Click to collapse
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed?
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.
elesbb said:
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD.
Click to expand...
Click to collapse
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
Click to expand...
Click to collapse
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed? .
Click to expand...
Click to collapse
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.
Click to expand...
Click to collapse
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?
lvpre said:
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
Click to expand...
Click to collapse
Yeah I am currently rooted with the U firmware BL4. I want to upgrade to Oreo, hoping for performance improvements, better battery, etc. But I guess since the Oreo U firmware is still BL4, I can just downgrade if I can't get root back.
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
Click to expand...
Click to collapse
I never mentioned a bootloop? Is this about something else? The point I am trying to address is the loss of Sprint connectivity after flashing eng boot. This is because of the packages that need to be disabled.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
Click to expand...
Click to collapse
So you flash everything, eng boot, and are currently rooted. You then flash the provided file via flash fire, factory reset, and now you no longer are able to connect to Sprint network? When you say "can't connect to Sprint network", are you referring to data or to Sprint network entirely? If you go under your "about phone" section, what does your IMEI and phone number display? Don't actually type it here, but it should be something comprehensible. It shouldn't say "unknown" or a bunch of zeros, etc. [/quote]
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
Click to expand...
Click to collapse
True..
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?
Click to expand...
Click to collapse
I do. A lot of people want to be back to BL4. There is NO difference in the newer bootloaders EXCEPT a special "key" type of thing that prevents downgrading. That is the only thing different. This is why the U firmware is still on BL4 despite having an Oreo update. Sprint changes the BL version just so people like us have extra hurdles to overcome when we want something different. Its very stupid tbh.
But, I would like to help you guys out, however, I AM NOT upgrading to the BL5/6. Noway nohow.
It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.
lvpre said:
It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.
Click to expand...
Click to collapse
Hmm. That's weird. What does your about phone section say for IMEI and phone number? Everything good? I wonder if something is affecting the PRL. Try updating that via settings menu before you flash the firmware and factory reset. The CSC shouldn't really affect that part. I have changed mine multiple times to just eff around and see what/if anything changed. Its more for the phone to know what menu options are available and such. For instance, call recording shows up when its not a US branded carrier.
Sadly I will never flash the newer BL. But I will definitely keep trying via the thread and if you would like to discord or something similar I would be down. School starts in about 2 weeks so I'm basically free till then
sim boot loop
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.
Aggiedude said:
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.
Click to expand...
Click to collapse
Thanks for posting this!!! I'm glad that I wasn't the only having this issue. I tried it again using a different method and still got the SIM boot loop. This method probably works great if you have anything other than Sprint or Sprint MVNO, but something is conflicting like it does during a typical root of the G930P. Anyway, hopefully, someone else will be able to figure this out.

Categories

Resources