Database Users

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???

How do I stop it from forcing an update?

I had to soft reset my phone about 5 minutes ago, as i was downloading the root files and the stinking phone tried to automatically update the software!
I have now unchecked the automatic check for updates, will that stop the madness?

EZ Package Disabler (Samsung)
Use that to disable "at&t software update", or something like that.

I appreciate your wanting to be help, but I need the package names to disable. I have disabled the FWupdate* app, and it still turns off my phone, and goes into the update, but fails, because of root. I want it to stop forcing the update. Is it one of the MDM apps? (mobile device management)?

grmcrkrs said:
I appreciate your wanting to be help, but I need the package names to disable. I have disabled the FWupdate* app, and it still turns off my phone, and goes into the update, but fails, because of root. I want it to stop forcing the update. Is it one of the MDM apps? (mobile device management)?
Click to expand...
Click to collapse
I disabled everything related to software update and knox. That is keeping me from updating.

fogame said:
I disabled everything related to software update and knox. That is keeping me from updating.
Click to expand...
Click to collapse
When you say everything, can you be more specific?

grmcrkrs said:
When you say everything, can you be more specific?
Click to expand...
Click to collapse
Although I left the two Knox apps enabled I believe you can block them as well. I'm on sprint so disable the software update ones and att software update. You should be good.

Decrypting loop after OTA update

Hello fellow people of XDA!
Today I got an OTA update for my S7 edge (SM-G935F). The update has installed fairly fast (after the first reboot). But then, it got stuck on a decrypting loop. I have enabled prior the full phone encryption, and set it to ask for a password at each start. I entered the password correctly, as it said Starting Android... after, and since then, only the rotating padlock is showing. Every like 5 minutes the soft buttons are lighting up for a second, but then nothing is happening. After a while it even gets hot, but still nothing. I had this issue at the previous update too, but it started after like 30-40 minutes. Now 90 minutes have passed and still nothing.
I can reboot to the recovery and bootloader screens, and everything is fine. Knox not tripped, not rooted, everything official. In the recovery screen it says that my CSC is ECT (but according to sammobile it should be CNX).
Some additional info: samsung/hero2ltexx/hero2lte
7.0/NRD90M/G935FXXU2DRAG
I will try to flash a stock rom (PDA: G935FXXS2DRAA, CSC: G935FROM1DQJ3). If that doesn't work, I'll flash today's rom (PDA: same, CSC: G935FVFG1DQI1).
Any tips/help would be greately appreciated! Would not want to fall to the wipe data method, because I don't want to lose everything... But then again, I guess that would remove the boot password...
Thanks!
Update: After waiting for like 10+ hours, nothing has changed. Maybe I shouldn't have forced a reboot after an hour of the ota update? Going to try flashing the firmware now.
Update 2: I flashed the firmware, now the buttons seem to light up less often. But after an hour of decrypting, I guess the ultimate soultion would be to do a factory reset, since no one is helping...

jaszfalvi.tamas said:
Hello fellow people of XDA!
Today I got an OTA update for my S7 edge (SM-G935F). The update has installed fairly fast (after the first reboot). But then, it got stuck on a decrypting loop. I have enabled prior the full phone encryption, and set it to ask for a password at each start. I entered the password correctly, as it said Starting Android... after, and since then, only the rotating padlock is showing. Every like 5 minutes the soft buttons are lighting up for a second, but then nothing is happening. After a while it even gets hot, but still nothing. I had this issue at the previous update too, but it started after like 30-40 minutes. Now 90 minutes have passed and still nothing.
I can reboot to the recovery and bootloader screens, and everything is fine. Knox not tripped, not rooted, everything official. In the recovery screen it says that my CSC is ECT (but according to sammobile it should be CNX).
Some additional info: samsung/hero2ltexx/hero2lte
7.0/NRD90M/G935FXXU2DRAG
I will try to flash a stock rom (PDA: G935FXXS2DRAA, CSC: G935FROM1DQJ3). If that doesn't work, I'll flash today's rom (PDA: same, CSC: G935FVFG1DQI1).
Any tips/help would be greately appreciated! Would not want to fall to the wipe data method, because I don't want to lose everything... But then again, I guess that would remove the boot password...
Thanks!
Update: After waiting for like 10+ hours, nothing has changed. Maybe I shouldn't have forced a reboot after an hour of the ota update? Going to try flashing the firmware now.
Update 2: I flashed the firmware, now the buttons seem to light up less often. But after an hour of decrypting, I guess the ultimate soultion would be to do a factory reset, since no one is helping...
Click to expand...
Click to collapse
Wait, i dont get it, it is prompting you for a password even you didnt set it?
Sent from my S7 Edge using XDA Labs

shah22 said:
Wait, i dont get it, it is prompting you for a password even you didnt set it?
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I set a password when I enabled Secure Startup.

jaszfalvi.tamas said:
I set a password when I enabled Secure Startup.
Click to expand...
Click to collapse
Then use that same password, i think there is confusion, there is a password when you enable fingerprint and then a password when you enable secure startup. Be sure not to confuse them. If it still happens, then I guess there's got something wrong with the update, and only way is a factory reset. Btw, i also updated and i normally entered secure boot password and it started okay. Don't know what caused this for you.
Sent from my S7 Edge using XDA Labs

shah22 said:
Then use that same password, i think there is confusion, there is a password when you enable fingerprint and then a password when you enable secure startup. Be sure not to remember them. If it still happens, then I guess there got something wrong with the update, and only way is a factory reset. Btw, i also updated and i normally entered secure boot password and it started okay. Don't know what caused this for you.
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I entered the password correctly, as it stated "Starting Android..." then the rotating padlock took forever. More than 10 hours even. But in the end, a factory reset helped me. But rip my photos and memories...

Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.

benjamen50 said:
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
Click to expand...
Click to collapse
Right, but i use encryption and i could update without any problem, don't know what caused this issue with him. But one should backup all data BEFORE updating, as i did to save yourself from such hassle.
Sent from my S7 Edge using XDA Labs

benjamen50 said:
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
Click to expand...
Click to collapse
Yeah, it's a sure thing I won't turn on Secure Stratup anymore. I don't know what OEM unlock does or does not, but right now, I don't have dev options enabled. If I had a microSD then I couldn't care less about resetting my phone, but since I don't have, because I have two SIM cards and a memory card has no place left, I feel bad.
Still, I don't know caused this issue. I had OTA updates before with full device encryption enabled and I had no issues before. I kinda used the same disk space at every OTA, so it should have took the same time... And I have to mention, that I did not tamper with the software. No root, no custom rom, and software only from the play store.

To enable developer options you click Build number 7 times which is located in the Software information tab in settings.
OEM unlock allows you to flash and boot the phone with custom binaries (Custom Recovery, Kernels, Roms). You can leave OEM unlock disabled if you don't want people that may steal your phone and use it for themselves.
With OEM unlock disabled and a google account signed in, it will block anyone from using the phone after a factory reset on stock Samsung firmware as it will prompt the user to enter the google account that was associated with that device.
Unfortunately there are rare cases that a OTA update may fail. Reflashing correct stock firmware usually fixes it but in worse case scenarios a factory reset will be required.

benjamen50 said:
To enable developer options you click Build number 7 times which is located in the Software information tab in settings.
OEM unlock allows you to flash and boot the phone with custom binaries (Custom Recovery, Kernels, Roms). You can leave OEM unlock disabled if you don't want people that may steal your phone and use it for themselves.
With OEM unlock disabled and a google account signed in, it will block anyone from using the phone after a factory reset on stock Samsung firmware as it will prompt the user to enter the google account that was associated with that device.
Unfortunately there are rare cases that a OTA update may fail. Reflashing correct stock firmware usually fixes it but in worse case scenarios a factory reset will be required.
Click to expand...
Click to collapse
Never had OEM unlock enabled, because I didn't know what is does, so thanks for the info. I reflashed the correct stock firmware, but that didn't help either, so I had to resort to wiping the data... Regarding this, do you know by any chance a good software for recovering data without root?

I don't know of any unfortunately, if anyone has any good paid ones that actually work please post here.

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.

Help with NFC Crashing - AT&T S8 Active

Hey,
Need some help. My brand new AT&T S8 Active arrived yesterday. Since I am located outside the US I'm stuck with utilising Odin to update the software.
The current version listed on the AT&T website was 5CSK1 and I was able to track down the update:
https://forum.xda-developers.com/showpost.php?p=81251867&postcount=743
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
I'm currently back on the latest K1 build.
Logcat shows errors with 'libnfc_nci' and a 'Fatal Exception' for the 'com.android.nfc' process. And to top it all off the NFC app is draining my battery.
If anyone can help me that would be awesome.

dchalkley said:
Hey,
Need some help. My brand new AT&T S8 Active arrived yesterday. Since I am located outside the US I'm stuck with utilising Odin to update the software.
The current version listed on the AT&T website was 5CSK1 and I was able to track down the update:
https://forum.xda-developers.com/showpost.php?p=81251867&postcount=743
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
I'm currently back on the latest K1 build.
Logcat shows errors with 'libnfc_nci' and a 'Fatal Exception' for the 'com.android.nfc' process. And to top it all off the NFC app is draining my battery.
If anyone can help me that would be awesome.
Click to expand...
Click to collapse
ugh, the active line... there hasnt ever been much support for those. All you can really do is keep flashing the stock firmware and hope that the errors resolve themselves.
Side note: have you noticed how they stopped making the active phones? They were a dismal failure. All they are is the regular phone in a case that you cant take off :/

dchalkley said:
Hey,
Need some help. My brand new AT&T S8 Active arrived yesterday. Since I am located outside the US I'm stuck with utilising Odin to update the software.
The current version listed on the AT&T website was 5CSK1 and I was able to track down the update:
https://forum.xda-developers.com/showpost.php?p=81251867&postcount=743
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
I'm currently back on the latest K1 build.
Logcat shows errors with 'libnfc_nci' and a 'Fatal Exception' for the 'com.android.nfc' process. And to top it all off the NFC app is draining my battery.
If anyone can help me that would be awesome.
Click to expand...
Click to collapse
Might try redownloading a different firmware from a differ location. I had this issue on a lg back in the day the camera wouldnt work no matter what I always restored stock with one firm I had. And it ended up being a bad download. Another possibility is a bad NFC chip. If it's new I'd have it warranted

Thankyou, Thankyou Youdoofus and TheMadScientist for your advice.
Woke up early today (3am) with coffee in hand I tried again downloading the K1 and J3 builds; neither worked.
Unfortunately there's no alternative download for them... Google points to the XDA forums which seem to come from some Russian forum.
I've gone to an earlier build - 5CSI3 - https://forum.xda-developers.com/showpost.php?p=80505887&postcount=186 which works.
So it's not a NFC chip issue, yay. Now, just need to figure out what I'll do when the next update hits at the end of this month.

dchalkley said:
Thankyou, Thankyou Youdoofus and TheMadScientist for your advice.
Woke up early today (3am) with coffee in hand I tried again downloading the K1 and J3 builds; neither worked.
Unfortunately there's no alternative download for them... Google points to the XDA forums which seem to come from some Russian forum.
I've gone to an earlier build - 5CSI3 - https://forum.xda-developers.com/showpost.php?p=80505887&postcount=186 which works.
So it's not a NFC chip issue, yay. Now, just need to figure out what I'll do when the next update hits at the end of this month.
Click to expand...
Click to collapse
Make sure your using the latest odin build 3.13. I dont have an active. **** I read it wrong so it does work on other builds?

TheMadScientist said:
Make sure your using the latest odin build 3.13. I dont have an active. **** I read it wrong so it does work on other builds?
Click to expand...
Click to collapse
Yeah, it's working on the 5CSI3 build from October 2019, there's been two recent updates since then (and another will come at the end of the month). I don't know what's happening as no one else has reported this issue .
Just wanting to be on the most recent version for security and the annoyance of having data wiped every update.
Edit: Yeah, Odin v3.13.1 . No errors being displayed, all green.

This issue is very likely to be caused by 3rd party sim unlock or FRP removal and meddling with knox.
I have been trying to get around this problem and it seems it is either a security measure to disable nfc payments on triggering knoxguard or problem with modem.
this problem started after CSJ3 update afaik and only on some phones, if someone can explain this would be great.
Solution:
You will lose all data so backup is recommended
Remove your SIM card, re-install the firmware with ODIN and check Nand Erase auto reboot and F. reset time
Check your KG status(checking or prenormal) on the bootloader, and in settings>device care you will see Security is disabled and it crashes when you click it.
I also noticed the settings menu is weird with many broken options and dailer codes dont work anymore.
EDIT: Workaround Solution:
THIS IS FOR G892A ONLY who have problem with NFC after updating to builds after December 2019
Disclaimer: do at your own risk and can break your phone signal or system detected as rooted/custom
note: you will lose all data, ONLY check "Auto Reboot" and "F. Reset Time" in odin
1) Backup your data
2) Delete your google account, so FRP : OFF in bootloader (this can cause problems if not done)
3) Flash 5 firmware files G892AUCS5CTC1 (latest rom with march 2020 security) and get back to bootloader
4) Flash 3 files from G892AUCS5CSI3 : BL, CP and CSC
(odin will say PASS, but recovery will give error)
5) select wipe data partition then reboot to system
when the phone starts you will see NFC logo in statusbar means you are successful
if you get errors while using odin: flash combination file : G892AUCU5ASD1 if this doesnt work it means you have different problem (cable, socket, pc, bad chip)
i tried flashing CP file only and phone booted into UPLOAD mode, so dont panic if you get into UPLOAD mode just reboot with 3 buttons to recovery and start over

Vcek said:
This issue is very likely to be caused by 3rd party sim unlock or FRP removal and meddling with knox.
I have been trying to get around this problem and it seems it is either a security measure to disable nfc payments on triggering knoxguard or problem with modem.
this problem started after CSJ3 update afaik and only on some phones, if someone can explain this would be great.
Solution:
You will lose all data so backup is recommended
Remove your SIM card, re-install the firmware with ODIN and check Nand Erase auto reboot and F. reset time
Check your KG status(checking or prenormal) on the bootloader, and in settings>device care you will see Security is disabled and it crashes when you click it.
I also noticed the settings menu is weird with many broken options and dailer codes dont work anymore.
EDIT: Workaround Solution:
THIS IS FOR G892A ONLY who have problem with NFC after updating to builds after December 2019
Disclaimer: do at your own risk and can break your phone signal or system detected as rooted/custom
note: you will lose all data, ONLY check "Auto Reboot" and "F. Reset Time" in odin
1) Backup your data
2) Delete your google account, so FRP : OFF in bootloader (this can cause problems if not done)
3) Flash 5 firmware files G892AUCS5CTC1 (latest rom with march 2020 security) and get back to bootloader
4) Flash 3 files from G892AUCS5CSI3 : BL, CP and CSC
(odin will say PASS, but recovery will give error)
5) select wipe data partition then reboot to system
when the phone starts you will see NFC logo in statusbar means you are successful
if you get errors while using odin: flash combination file : G892AUCU5ASD1 if this doesnt work it means you have different problem (cable, socket, pc, bad chip)
i tried flashing CP file only and phone booted into UPLOAD mode, so dont panic if you get into UPLOAD mode just reboot with 3 buttons to recovery and start over
Click to expand...
Click to collapse
Hello There!..kind of new about this so..long story short..
Phone had Android 8, and I really love Night mode on Android 9, so...I've found BL, AP, CP, CSC, USER Data ROM for GALAXY S8 ACTIVE AT&T Unlocked, however..I am a little bit afraid of any NAND Erase.
I am not an expert, but I can tell you are. By any chance do you have any vide or graphic tutorial abot how you can perform these actions? It is very odd that I am unable to have any *# codes working, and lately, I've received this odd message about NFC Service has stopped, so...any graphic step by step guide will be highly appreciated it.
I've tried ....soft reset, then factory reset, then flash again ODIN (BL, AP,CP, CSC and USER DATA ) But I have no idea how to back up my data, and it will be very helpful to have G892AUCS5CSI3 as well.
Thank you very much for your time, I hope you can help me and I appreciate very much your time.
The one that I have is AP_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar
BL_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CP_G892AUCS5CTC1_CP15398738_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CSC_ATT_G892AATT5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
USERDATA_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar

SOLVED!
So...I've followed the steps to install only BL, CP and CSC using G892AUCS5CSI3...however, the system started as usual, and actually did not work =(
RESOLUTION:
INSTALL THE FULL G892AUCS5CSI3. Worked as magic =)
thank you for the thread!!

moncd6 said:
Hello There!..kind of new about this so..long story short..
Phone had Android 8, and I really love Night mode on Android 9, so...I've found BL, AP, CP, CSC, USER Data ROM for GALAXY S8 ACTIVE AT&T Unlocked, however..I am a little bit afraid of any NAND Erase.
I am not an expert, but I can tell you are. By any chance do you have any vide or graphic tutorial abot how you can perform these actions? It is very odd that I am unable to have any *# codes working, and lately, I've received this odd message about NFC Service has stopped, so...any graphic step by step guide will be highly appreciated it.
I've tried ....soft reset, then factory reset, then flash again ODIN (BL, AP,CP, CSC and USER DATA ) But I have no idea how to back up my data, and it will be very helpful to have G892AUCS5CSI3 as well.
Thank you very much for your time, I hope you can help me and I appreciate very much your time.
The one that I have is AP_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar
BL_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CP_G892AUCS5CTC1_CP15398738_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CSC_ATT_G892AATT5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
USERDATA_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
Click to expand...
Click to collapse
You can backup your data with Samsung backup and restore to Samsung cloud or to your PC with Samsung's Smart Switch app.
As for tutorial I'll try to make one with images for the latest ROM G892AUCU5CTF4 dated 20-Aug-2020 with August security patch. I'll upload it later as I still have to backup my phone before updating.

Thanks!
Thank you so much!
Is it G892AUCU5CTF4 a estable versión for S8 Active? Or does it has any other bugs? I had to "downgrade" and now things are pretty cool, however, I would love to have the newest version. Thank you!

moncd6 said:
Thank you so much!
Is it G892AUCU5CTF4 a estable versión for S8 Active? Or does it has any other bugs? I had to "downgrade" and now things are pretty cool, however, I would love to have the newest version. Thank you!
Click to expand...
Click to collapse
It doesn't have any bugs but some people have issue with flashing new builds, if you have this issue just install CSI3 build or earlier

dchalkley said:
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
... And to top it all off the NFC app is draining my battery.
Click to expand...
Click to collapse
Same. I also tried CTA2 and CTL1. Everything after CSI3 has NFC crashing and excessive battery drain. I've tried multiple flashes on multiple phones.
dchalkley said:
I tried again downloading the K1 and J3 builds; neither worked.
Unfortunately there's no alternative download for them... Google points to the XDA forums which seem to come from some Russian forum.
I've gone to an earlier build - 5CSI3 - https://forum.xda-developers.com/showpost.php?p=80505887&postcount=186 which works.
So it's not a NFC chip issue, yay. Now, just need to figure out what I'll do when the next update hits at the end of this month.
Click to expand...
Click to collapse
Same.
dchalkley said:
I don't know what's happening as no one else has reported this issue .
Edit: Yeah, Odin v3.13.1 . No errors being displayed, all green.
Click to expand...
Click to collapse
Same here. I used Odin 3.14.1, though.
Vcek said:
Solution:
You will lose all data so backup is recommended
Remove your SIM card, re-install the firmware with ODIN and check Nand Erase auto reboot and F. reset time
Click to expand...
Click to collapse
This did not work for me, not even with "Nand Erase" checked.
moncd6 said:
It is very odd that I am unable to have any *# codes working, and lately, I've received this odd message about NFC Service has stopped, so...
Click to expand...
Click to collapse
Same. The problem of the secret dialer codes not working parallels the NFC problem for me; that is to say that it doesn't work on any firmware after CSI3.

moncd6 said:
SOLVED!
So...I've followed the steps to install only BL, CP and CSC using G892AUCS5CSI3...however, the system started as usual, and actually did not work =(
RESOLUTION:
INSTALL THE FULL G892AUCS5CSI3. Worked as magic =)
thank you for the thread!!
Click to expand...
Click to collapse
Can you please upload G892AUCS5CSI3? it's all dead links i got

rerenz said:
Can you please upload G892AUCS5CSI3? it's all dead links i got
Click to expand...
Click to collapse
Same. I'm not sure where I originally got it from, but here's a reupload from my archives. I created a list of MD5 checksums if you care to check the five files for corruption.

voidxor said:
Same. I'm not sure where I originally got it from, but here's a reupload from my archives. I created a list of MD5 checksums if you care to check the five files for corruption.
Click to expand...
Click to collapse
Finally, it works! My NFC is back. Thanks, pal.