[AT&T Samsung Galaxy S 4 General] polish_pat:
Here is a method that can potentially let you OTA and keep root, try at your own risk:

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​

For the past few weeks, i've been on a quest to get root and have official status. I've created a few thread related to the issue, and out of all the people that responded, only one has given me the answer that worked.

Still today, i stumble across many people with the custom status issue a little everywhere in the forum, so maybe having one thread explaining it would be a good idea.

This thread is for those that want OTAs, that wanna stay stock but just have root, and that switching from Superuser to SuperSU and rebooting twice did not work.

This has the best chances of working for those who are stock and rooted with no custom or kernel recovery and just want OTAs. It has also been reported to work with stock, custom kernel and/or recovery and even those with custom ROMS (but if you have custom ROM, OTAs should not be your priority

These methods have been tested with i337 (US Version) and i337m (Canadian Version) and have been, for most, a permanent solution.

You can start by Method 1 or 2, ONLY USE METHOD 3 or 4 as a final solution as it has a danger of hard-bricking your device.

Method 1:

REPLACE SUPERUSER WITH SUPERSU BEFORE YOU DO THIS!!!​

Step 1: Download ES File Explorer

Step 2: Open ES and press Menu key on phone (grant root when asked)

Step 3: Click Tools -> Root Explorer

Step 4: Click Mount R/W and select RW for all options and click OK

Step 5: Click / on top

Step 6: Navigate to System -> xbin and delete Busybox

Step 7: Reboot x2

Step 8: Once that OTA comes, simply use rootkeeper to freeze it up, update and restore root

Method 2:

Root with motochopper​

Step 1: Download ES File Explorer

Step 2: Open ES and press Menu key on phone (grant root when asked)

Step 3: Click Tools -> Root Explorer

Step 4: Click Mount R/W and select RW for all options and click OK

Step 5: Click / on top

Step 6: Navigate to System -> xbin and delete Busybox

Step 7: Install SuperSU, let it update binary and remove other superuser app

Step 8: Went into SuperSU settings and un-check "Enable Superuser"

Step 9: Reboot x2

Step 10: Once that OTA comes, simply use rootkeeper to freeze it up, update and restore root

Method 3:

THIS IS A DANGEROUS OPERATION AND COULD POTENTIALLY BRICK YOUR DEVICE. PROCEED AT YOUR OWN RISK. A USB JIG IS PREFERRED IF YOU HAVE A WORKING ONE.

( and by brick I mean brick - only a board replacement or a JTAG unit will be able to save you, don't mess with boot(loader) stuff unless you really mean it! )

REPLACE SUPERUSER WITH SUPERSU BEFORE YOU DO THIS!!! This method only works on stock firmware & recovery.​

Step 1: Download Triangle Away from playstore

Step 2: Open and grant root

Step 3: Confirm your device

Step 4: Download Add-On

Step 5: Hit "Reset Flash Counter"

Step 6: Once it reboots, hit "Volume Up" to reset flash counter

Method 4:

Special thanks to Aou, 0tt0m@n and dwitherell

This method is a sure method. This eliminates the source of the custom status itself. SysScope is the system app that scans for files that are potentially on a custom phone, once one of those files is detected, it triggers the "Custom Status" and lock at boot. This method eliminates that scanner. It's possible that you already have to have an Official status for this to work, the OP of the thread will look into the issue, please follow his thread closely for more info​

Step 1: Head over to the "Removing SysScope Thread" in the dev section or just click the link and follow his instructions

Step 2: Thank Aou

Thanks to everybody that has given their feedback and help develop this thread into a multi-method solution.

Credit to: haloimplant (for method 2), Chainfire (for method 3), Aou 0tt0m@n and dwitherell (for method 4)

I hope one of these has works for you, Thumbs up if it did!:good:​