Database Develop

[Q] Custom Device Status

I have rooted my note 3 via towelroot (thank you so much geohot!!!). I have installed exposed framework, supersu, busybox and safestrap. Here is the question: my note switches from device status custom to official. On some boots it will have the custom status icon on screen. Some boots it does not. This corresponds to the system info as well....sometime shows custom and sometimes official. Why is this? Its no big deal i'm just curious. Thanks.

mrcoffee1985 said:
I have rooted my note 3 via towelroot (thank you so much geohot!!!). I have installed exposed framework, supersu, busybox and safestrap. Here is the question: my note switches from device status custom to official. On some boots it will have the custom status icon on screen. Some boots it does not. This corresponds to the system info as well....sometime shows custom and sometimes official. Why is this? Its no big deal i'm just curious. Thanks.
Click to expand...
Click to collapse
Once you rooted you customized the software. That custom padlock logo is a tattle tale telling on you! I believe your using an xposed module to "fake system status" in order to fool certain people. The xposed module is failing when you see this. It's possible an update, or setting was applied to the module making it fail. Or maybe it's losing it's superuser rights. I had the same thing happen to me. I used triangle away and haven't seen it again. It will surely come back on a factory reset I'm sure.

This happened to me as well and I know its not the xposed because I checked it. This has only happened 3 times and has not happen in like 4 days I checked my system and it says everything is official it did say custom the 3 times it happened I did do a factory reset and it still says official my question is has anyone found a way to unroot for warranty porpoises? Su will not unroot towelroot from what im seeing ...but if everything says official would you even need to worry about unrooting lol I mean if u just factory reset and sent it back I shows no sign of root its all official and no knox tripped ..just a thought ..

Triangle Away
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway
Sent from my SM-N900A using XDA Free mobile app

Freezing "sysscope " on my sgs4 removed the custom unlock boot logo /icon like a charm, however it still bounces back and forth between official and custom on device status when looking.

mrcoffee1985 said:
I have rooted my note 3 via towelroot (thank you so much geohot!!!). I have installed exposed framework, supersu, busybox and safestrap. Here is the question: my note switches from device status custom to official. On some boots it will have the custom status icon on screen. Some boots it does not. This corresponds to the system info as well....sometime shows custom and sometimes official. Why is this? Its no big deal i'm just curious. Thanks.
Click to expand...
Click to collapse
Remove "busy box" file in XBIN system folder. Found this solution on a "Galaxy S4" forum. For a some reason a system keeps some leftovers after the full recovery done. Kinda wrong.

Kernel is not seandroid enforcing set warranty bit: kernel

So i just finished the process of rooting my s2 tablet 810 5.1.1 and every time i reboot or turn the phone on and off i notice a message that says
"Kernel is not seandroid enforcing
set warranty bit: kernel"
Ive done some google searches and i would like to think its normal becuase i read in a thread that this is because of the knox trip.
however i also see threads dedicatied on how to resolve this "issue"
As some of you guys might already know if the version is 5.1.1, then you need a kernel to load during the process of root.
when i attempted to root the first time the kernel boot did not restart my tablet for me, so i manually restarted even though the option was set to auto-reset.
I now believe the process was incomplete because the tablet entered a boot loop after i ran the auto-root file. (Failed 1st attemp)
Second attempt i ran the kernel file and then the tablet rebooted successful, howver THIS is when the "Kernel is not seandroid enforcing set warranty bit: kernel"
is something wrong or is all good? gonna check if i have root after this post.
SIDE QUESTION
in the thread of the guy who posted about how to root he mentions how to put a custom recovery. Is that mandatory? or can i do this later when i want to install a custom ROM?
will post agian if anything important comes up after i check if ROOT

Okay so something interesting did come up. It seems i am rooted, however i keep getting a notification that an unauthorized action haas been taken and i must click on a restart to undo the changes that have been done.
its kind of annoying because it keeps popping up. I assumw this is the knox security.
there is an option for "sperate work and play" where i can install knox app in a safe and isolated space. what is this?
should i just ignore this poppup ? or is there a way to get rid of it?
someone to talk to would be nice right now .

This is because your kernel was modified to be permissive in order to root your tablet.
Installing a custom recovery is a must and one of the main reasons of a rooted device, it will give you the possibility of making/restoring backups, installing apps and ROMs between other stuff.
The anoying pop-up can be disabled by freezing/uninstalling SecurityLogAgent
Sent from my SM-T810 using Tapatalk

danyvw said:
This is because your kernel was modified to be permissive in order to root your tablet.
Installing a custom recovery is a must and one of the main reasons of a rooted device, it will give you the possibility of making/restoring backups, installing apps and ROMs between other stuff.
The anoying pop-up can be disabled by freezing/uninstalling SecurityLogAgent
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
I understand what a custom recovery does, ive had it on my two previous phones and have tried TWRP and CW.
however i only installed them because i wanted to flash a custom rom on those two phones. With my s2 tablet im looking to just stay with root for now, that is why i am asking if the custom recovery is a must? because i dont see any use for it if i am just going to keep my tablet rooted and not flash any roms yet
also any idea on how to get rid of that pop up in notification saying i must click the restart to undo the changes that have been made

danyvw said:
This is because your kernel was modified to be permissive in order to root your tablet.
Installing a custom recovery is a must and one of the main reasons of a rooted device, it will give you the possibility of making/restoring backups, installing apps and ROMs between other stuff.
The anoying pop-up can be disabled by freezing/uninstalling SecurityLogAgent
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
Originally I said I froze and unistalled SecurityLogAgent, however I did not. So I did it now. I will report back if I go error free.
Thank you!
I am having this same issue. I have twrp recovery installed, I have disabled/unistalled everything with knox security symbol . I continue to get this error. I have wiped everything and started fresh and cannot get rid of this error. The second problem i am having, I cannot reinstall those apps with TB, I tried each of them and I even let it set overnight while I slept and it was still going when I woke up.....
1. How can I get rid of this error?
2. If I can't how can i get tb to reinstall knox or can I unroot without having these reinstalled?
this is everything I have froze, backed up, and unistalled
BBCAgent 2.0
com.samsung.android.bbc.fileprovider
com.samsung.knox.kss
com.sec.knox.containeragent2
com.sec.knox.packagegeverifier
com.sec.knox.sortcutsms
com.sec.knox.switcher
KLMS Agent 2.5.312
KNOX 2.3.0
KNOX II 2.3.0
KNOX SetupWizardClient 2.3.0
KnoxFolderContainer2.4.0

Getting rid of all Knox apps is good when you are rooted but the anoying pop-up comes from SecurityLogAgent app and not from Knox apps, as soon as you freeze or uninstall it the message will stop.
Sent from my SM-T810 using Tapatalk

Lost root access after a week, possibly by entering "smart manager"

I got a note 5 SM-N920W8 Telus last week. First thing i did was to upgrade to marshmallow, and then root it. I rooted it fine, wiping the phone in the process of installing the custom recovery. Now i've used plenty of apps that require root, and all have worked fine. About 15 minutes ago I try to go in "Ad away" to disable it temporarily to check if firefox was gonna to react faster on loading pages (it seemed so fast last week, but sluggish lately) only to find out Ad away is complaining I dont have root access anymore. So I go and check in SU , and sure enough, he also complains I don't have root. Marshmallow 6.0.1
Who deleted my root?
The only thing different I recall doing on my phone recently, and could coincide with me not noticing it between 2 apps that need root, was that in the settings, I went into "Smart manager". In there, I was curious to see what this "Device Security" (deactivated) could hold.
Anyone else has had their root removed? Or is there anything else I should look out for , background process or something , that targets my root? I just reflashed it, and it works fine again, but that just never happened to me before..

I have the same problem?? Did you get any answer from any body? Do I have to re root again?

Just flash super su in recovery. Same thing happened to me and i don't know what is the cause of the problem

Roamin64 said:
I got a note 5 SM-N920W8 Telus last week. First thing i did was to upgrade to marshmallow, and then root it. I rooted it fine, wiping the phone in the process of installing the custom recovery. Now i've used plenty of apps that require root, and all have worked fine. About 15 minutes ago I try to go in "Ad away" to disable it temporarily to check if firefox was gonna to react faster on loading pages (it seemed so fast last week, but sluggish lately) only to find out Ad away is complaining I dont have root access anymore. So I go and check in SU , and sure enough, he also complains I don't have root. Marshmallow 6.0.1
Who deleted my root?
The only thing different I recall doing on my phone recently, and could coincide with me not noticing it between 2 apps that need root, was that in the settings, I went into "Smart manager". In there, I was curious to see what this "Device Security" (deactivated) could hold.
Anyone else has had their root removed? Or is there anything else I should look out for , background process or something , that targets my root? I just reflashed it, and it works fine again, but that just never happened to me before..
Click to expand...
Click to collapse
Im having similar issues. 6.0.1 on my tmo note 5 rooted perfectly using Max Lee's method. However as soon as I rooted and transfered all my data back I did a nandroid backup. Happen to wipe my phone the other night and and restored the nandroid backup and as soon as it restored I lost root. Happens everytime I restore even a newer nandroid in twrp. Never had this happen on any root method on any note.

WTF..
It's happened again this morning.. Root dissapeared by itself. The only recent thing I can think I did , was buying a game (The cave) from play store last night.
Any way to identify what is removing SU ?

Flash SuperSU 2.74 and delete 'SecurityLogAgent'

I also lost root
I have a Samsung Galaxy Note 5 on the Sprint Network. I just now noticed that my applications that require root access, including Titanium Backup are reporting that my device is no longer rooted. Weird. This has never happened in the past when I had rooted Samsung phones. I will re-flash the Super User file as instructed in this thread and see if that resolves the issue.
---------- Post added at 03:01 AM ---------- Previous post was at 02:32 AM ----------
Per your insstuctions, I reflashed SuperSU 2.74 using TWRP. Then once my Note 5 rebooted, I launched Titanium Backup and found "SecurityLogAgent" and uninstalled it. However, in order for me to access TWRP I have to reinstall it using ODIN and immediately after I get the green "PASS" light in ODIN I have to quickly do the 'three finger' button press to launch TWRP. Weird....
Anyway, so far so good.
Thank you.
Battlehero said:
Flash SuperSU 2.74 and delete 'SecurityLogAgent'
Click to expand...
Click to collapse

Has a permanent solution been found? I am suffering the same inexplicable loss of root. International N910F on stock.

Bosbouer said:
Has a permanent solution been found? I am suffering the same inexplicable loss of root. International N910F on stock.
Click to expand...
Click to collapse
Yes, follow Battlehero's instructions (post #6) worked fine for me.

Roamin64 said:
Yes, follow Battlehero's instructions (post #6) worked fine for me.
Click to expand...
Click to collapse
Thanks that worked to a certain extent. Titanium requesting root privileges for backup would still pop up as failed. Checking root would show as unrooted. The Superuser app was updated on the 5th of July 2016. Since I applied that update, i have not lost root on any of my devices.

Apps refuse to start because phone being rooted but it isn't!

At least 2 of my Apps refuse to start. One is my banking app and they do not offer any other way of interaction.
The problem is that the phone in fact is not rooted! It's just "OEM unlocked" to be prepared for root (which I need for E.g. titanium backup, but only maybe once a month).
Please give me a way out of this vicious circle!
I cannot remove the OEM unlock because it requires full wipe every time. Or is there a way?
Or what can I possibly tell the App Provider to improved their Code so that Oneplus phone state is being recognized (more) correctly?
Any help would be greatly appreciated.

Use Magisk I guess? Use it to hide root from that app.

Reeb_Lam said:
Use Magisk I guess? Use it to hide root from that app.
Click to expand...
Click to collapse
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?

ako673de said:
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
Click to expand...
Click to collapse
You need to do some reading about Safetynet. If you're OEM unlocked you fail Verified Boot checks. Most custom Kernels include a bypass for this. Magisk alone should also work. I think you missed one important step:
Open Play Store Settings. Scroll down. It says 'Uncertified' at the bottom, right? Now install and set up Magisk. Go to system App Settings and clear Data and Cache for Play Store. Return to the Play Store Settings and scroll down. Now it should say 'Certified'. It might not be immediate, but it will happen. Now your Banking Apps work.
If you don't want, or have no luck with Magisk, simply flash a Custom Kernel that bypasses Verified Boot, and works with OOS.
Simple.

Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?

ako673de said:
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
Click to expand...
Click to collapse
Link to other Thread?
I don't know Magisk but are you hiding Root from your Banking App? Have you cleared Data and Cache for the Banking App since getting Certified?

First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?

ako673de said:
Any other idea?
Click to expand...
Click to collapse
Nope. If Play Store says Certified you should be good to go. I can only imagine it's a Magisk issue. Post screenshots of your config and let the Magisk experts pick through them. Maybe there's something not set up correctly.

ako673de said:
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
Click to expand...
Click to collapse
Hide Magisk Manager. I had to do that to get my banking app to work.
Edit: you may need to reboot after hiding Magisk Manager and clear you banking app's data before it works.
Sent from my OnePlus3T using XDA Labs

Thank you, indeed that WORKED! Well, at least for 2 out of 3 Apps. I think I can tell which one: "HVB banking". Maybe could somebody cross-check this one on his/her phone?

After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?

ako673de said:
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
Click to expand...
Click to collapse
Did you reflash custom kernel after update?

I'm not using any. What I did right after the update is to disable dm-verity (with a patched boot.img), like I did last time. But magisk is not yet re-installed because I wanted to see at least once the HypoVereinsbank App working, which it in fact does (different to last time when the phone was not rooted as well, and the store not certified!).

ako673de said:
But magisk is not yet re-installed
Click to expand...
Click to collapse
That's why... You can't pass the ctsProfile check if your bootloader is unlocked, and if you can't pass the ctsProfile check the Play Store won't be certified. You need Magisk for that...

Now I'm getting confused. The initial mail of this thread explains the situation as it was when I opened this thread:
--> Original ROM, no root, and banking apps didn't work <--
The advice to clear data of the PlayStore immediately brought the PlayStore back to "certified".
This is clearly in contrast to what you're saying now.
I can imagine only one reason: Maybe the older PlayStore had a bug and therefore was able to "certify" even with unlocked bootloader?
Sidenote: My main intention to do the firmware upgrade was that the "safety net checks" in Magisk suddenly stopped working one day (with the error message "invalid response", most probably you know what I'm talking about, I've read some comments from you on this issue). Therefore it's maybe really not too unlikely that Google has changed something very basic. Could you please confirm?
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).

ako673de said:
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_The_response_is_invalid

Sorry, now comes a probably often asked question: do I need the safetynet check option in magisk for something real? Or do the alternative apps fulfill all possible needs? What are these needs? Isn't that exactly what the PlayStore does to determine "certified"?

After quite some months of absolutely no "root" problems with any of my apps, since today o2banking again doesn't work.
I tried to update Magisk, but after update of the Magisk manager app to v7.1.1(203) it reports that Magisk is not installed at all, and any update of Magisk itself resulted in just the same. So I reverted back to v6.1.0(165) and everything seems to be okay, except that o2banking doesn't work. SafetyNet is clean, Magisk is hidden for o2banking and Magisk manager is repacked.
Does anybody know what the problem might be? Especially with that new version of the manager app, but also with Magisk v19.0 which cannot be installed from v6.1.0 (max. is v18.1). Any ideas welcome! I'm now on OOS 5.0.8 by the way.
SOLVED it myself: As mentioned somewhere in the update FAQ of Magisk there was a bug in manager v6.1.0 that causes the updated v7.1.1 to co-exist with the old version if the old version has been re-packed. If anybody encounters the same problem, the solution is at the bottom of this page: https://www.didgeridoohan.com/magisk/ManagerIssues.
o2banking will then still not work. Update to v19.0 is mandatory. But that is no problem then any more...

probably your banking app identified oxygen os as custom rom and have root. 1 out of 3 banking app in my phone doesn't work with lineageos even though i already hide magisk, but when running oxygen os with magisk hide, and also hide magisk manager (turn it on in magisk manager setting) all 3 banking app work just fine. maybe try sending a message to bank app developer to add oxygen os as exception.

Did you notice my edit? It was a problem with magisk manager update and magisk main version. Now everything is back up and running.

New update is up for Nokia 5.1 plus

I have noticed a new update is available for our devices. There isn't much detail but it seems it isn't just a security update.
V2.20A

Ilgazc said:
I have noticed a new update is available for our devices. There isn't much detail but it seems it isn't just a security update.
V2.20A
Click to expand...
Click to collapse
I have received the update as well, although I just updated to the pie update from Oreo yesterday, I noticed that night mode isn't working (is it the same for you) - thinking of performing a factory reset
Also is your device rooted? Cus I can see the magisk icon on your status bar.
Thank you.

keonramses said:
I have received the update as well, although I just updated to the pie update from Oreo yesterday, I noticed that night mode isn't working (is it the same for you) - thinking of performing a factory reset
Also is your device rooted? Cus I can see the magisk icon on your status bar.
Thank you.
Click to expand...
Click to collapse
Hello
There isn't any global dark mode, I heard it is coming in Android 10. Google keeps adding dark mode to their apps though.
It is rooted through the "temp root solution". System and boot partition are still locked and Magisk is stuck on a old version. I just use it for titanium backup etc.

Ilgazc said:
Hello
There isn't any global dark mode, I heard it is coming in Android 10. Google keeps adding dark mode to their apps though.
It is rooted through the "temp root solution". System and boot partition are still locked and Magisk is stuck on a old version. I just use it for titanium backup etc.
Click to expand...
Click to collapse
Thanks I was able to get it working, do you have any modules working well with it (what are they?), Trying to set up edxposed (so I can use lucky patcher) without luck

Ilgazc said:
Hello
There isn't any global dark mode, I heard it is coming in Android 10. Google keeps adding dark mode to their apps though.
It is rooted through the "temp root solution". System and boot partition are still locked and Magisk is stuck on a old version. I just use it for titanium backup etc.
Click to expand...
Click to collapse
How did you get titanium backup running? it keeps saying it can't detect root.

keonramses said:
I have received the update as well, although I just updated to the pie update from Oreo yesterday, I noticed that night mode isn't working (is it the same for you) - thinking of performing a factory reset
Also is your device rooted? Cus I can see the magisk icon on your status bar.
Thank you.
Click to expand...
Click to collapse
keonramses said:
How did you get titanium backup running? it keeps saying it can't detect root.
Click to expand...
Click to collapse
It runs fine here however you can lose the entire root (super user) functionality unless you reboot sometimes. I think phone's hard core power manager kills Magisk sometimes. When it happens Magisk will say new version is available.
BTW I use this root method:
https://forum.xda-developers.com/nokia-x5/how-to/temp-root-solution-nokia-5-1-plus-t3948577

keonramses said:
Thanks I was able to get it working, do you have any modules working well with it (what are they?), Trying to set up edxposed (so I can use lucky patcher) without luck
Click to expand...
Click to collapse
Some users report some stuff working but as there is no TWRP and Magisk manager shell, I am afraid to test things. Basically anything running early will fail, think like running a NT service vs running on user login. This thing runs very late for any advanced hack to work.

Ilgazc said:
It runs fine here however you can lose the entire root (super user) functionality unless you reboot sometimes. I think phone's hard core power manager kills Magisk sometimes. When it happens Magisk will say new version is available.
BTW I use this root method:
https://forum.xda-developers.com/nokia-x5/how-to/temp-root-solution-nokia-5-1-plus-t3948577
Click to expand...
Click to collapse
It's the same method I followed to get root, but titanium isn't detecting it, I attached a screenie

Help Apps being killed
Guys please I need help l my apps that I want to run are being killed, email WhatsApp Adguard etc