Hi guys i have rooted my phone recently and am on a custom rom now, but anytime i power on the phone i get this unfamiliar message that states.
Kerne is not seandroid enforcing
Set warranty Bit: Kernel.
please help!!
Sent from my GT-I9505 using XDA-Developers mobile app
Not A Problem
That is not an error it is simply stating that your SEANDROID is not enforcing meaning that more of the phones Sandbox has been disabled meaning that apps can do more than just with superuser access dont worry about it is normally fine.
My GT-i9505 Displays that on every boot and every Recovery Boot as i have TWRP installed and Resurrection Remix (2.7 (Android 6.0.1)) as the OS honestly its fine
-- Calsam12
calsam12 said:
That is not an error it is simply stating that your SEANDROID is not enforcing meaning that more of the phones Sandbox has been disabled meaning that apps can do more than just with superuser access dont worry about it is normally fine.
My GT-i9505 Displays that on every boot and every Recovery Boot as i have TWRP installed and Resurrection Remix (2.7 (Android 6.0.1)) as the OS honestly its fine
-- Calsam12
Click to expand...
Click to collapse
Ohh okay thanks very much
Sent from my GT-I9505 using XDA-Developers mobile app
Related
Hi everybody
I am owner of S4 LTE (GT-I9505) with fw version XXUEMJ7.
I followed the instructions for rooting the phone using the correct files fo my phone's version.
I installed the TWRP recovery but I have the following problems:
1. SuperSu does not appear in my apps drawer.
2. Knox is still active.
3. Titanium Backup stuck trying get root permission and the same time I receive knox message on ststus bar.
4. Root Checker stuck and I receive knox message on the status bar.
5. Knox disabler is ineffective.
6. Terminal program is ineffective too and when I try su command I receive knox message again.
Is it safe to full wipe my phone and install an AOSP rom or there is any posibility to brick my phone?
TWRP recovery seems to work properly.
Sent from my GT-I9505 using XDA Premium HD app
pannik72 said:
Hi everybody
I am owner of S4 LTE (GT-I9505) with fw version XXUEMJ7.
I followed the instructions for rooting the phone using the correct files fo my phone's version.
I installed the TWRP recovery but I have the following problems:
1. SuperSu does not appear in my apps drawer.
2. Knox is still active.
3. Titanium Backup stuck trying get root permission and the same time I receive knox message on ststus bar.
4. Root Checker stuck and I receive knox message on the status bar.
5. Knox disabler is ineffective.
6. Terminal program is ineffective too and when I try su command I receive knox message again.
Is it safe to full wipe my phone and install an AOSP rom or there is any posibility to brick my phone?
TWRP recovery seems to work properly.
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
Same here i want to get rid of knox notification i don't care about knox trip or whatever i just want my phone rooted help me please ..
Hi everybody
Finally I flashed this rom via ODIN
http://forum.xda-developers.com/showthread.php?t=2250824&highlight=xxuemj7
And then liquidsmooth rom with TWRP recovery.
Everything looks to work smooth.
pannik72 said:
Hi everybody
I am owner of S4 LTE (GT-I9505) with fw version XXUEMJ7.
I followed the instructions for rooting the phone using the correct files fo my phone's version.
I installed the TWRP recovery but I have the following problems:
1. SuperSu does not appear in my apps drawer.
2. Knox is still active.
3. Titanium Backup stuck trying get root permission and the same time I receive knox message on ststus bar.
4. Root Checker stuck and I receive knox message on the status bar.
5. Knox disabler is ineffective.
6. Terminal program is ineffective too and when I try su command I receive knox message again.
Is it safe to full wipe my phone and install an AOSP rom or there is any posibility to brick my phone?
TWRP recovery seems to work properly.
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
You can't because of KNOX, install a Pre-Rooted Rom instead.
BillvanHalen said:
You can't because of KNOX, install a Pre-Rooted Rom instead.
Click to expand...
Click to collapse
I did it.
First I installed the pre-rooted XXUEMJ7 rom and TWRP recovery with ODIN.
Then I downloaded Liquidsmooth v2.37 and flashed via TWRP.
Everything is fine now and Liquidsmooth rom works very well.
Hello, i have one samsung SM-J500H running on 5.1.1....i tried to root it but then i get error "recovery is not seandroid enforcing". I need to root it, what to do?
andrew21 said:
Hello, i have one samsung SM-J500H running on 5.1.1....i tried to root it but then i get error "recovery is not seandroid enforcing". I need to root it, what to do?
Click to expand...
Click to collapse
Follow This Guide:
http://forum.xda-developers.com/galaxy-j5/how-to/tutorial-upgrade-j5-2015-to-6-0-t3443904
Thanks ? Will try it out and let you know
Forgot to mention i flashed my SM-J500H with 5.1.1 4 files firmware...now when phone boots up i get error "Unfortunately, 360 Security Lite has stopped", i guess i will have to uninstall the app but there is no uninstall option in the app in applications manager, any suggestions?
Running a 900R4; CM14.1 Klteusc nightly 12-18; latest TWRP recovery.
Getting the aforementioned error when phone boots.
Everything boots and runs fine, but I'm a stickler for cleanliness and order. Anyone have a fix for this? I'm not experienced enough to go poking around with my kernel, I'm sure I'm not the only one with this problem.
Thanks in advance, gurus!
to fix this U must change SELINUX mode from permissive to enforcing.
the enforcing is a security layer build to android OS,SELINUX ENFORCING must be disabled if you installed Viber4Android.
If you insttalled V4A Donot change SELINUX to enforcing, V4A needs it.
but if you donot install it you can change the SELINUX TO ENFORCING.
To change it, There is an app called SELINUX mode changer
Sent from my SM-G532F using Tapatalk
yazeed_twb said:
to fix this U must change SELINUX mode from permissive to enforcing.
the enforcing is a security layer build to android OS,SELINUX ENFORCING must be disabled if you installed Viber4Android.
If you insttalled V4A Donot change SELINUX to enforcing, V4A needs it.
but if you donot install it you can change the SELINUX TO ENFORCING.
To change it, There is an app called SELINUX mode changer
Click to expand...
Click to collapse
I installed and ran, but the initial window had the "enforcing" option grayed out. I assume it's already enforcing, as the phone is working properly, I just want rid of the warning in case I decide to sell the phone.
Update: switched from stock Kernel to Boeffla Venom Kernel and the message is gone.
Hi,
I could really use some help here with the i377m Canadian S4.
Basically, I want to make sure there is no root, that the bootloader is locked and that SafetyNet passes.
Here is what I did:
1) Downloaded Optimized LineageOS 14.1 and GApps, copied them on an SD card
2) Installed Samsung drivers and Odin
3) Installed the recommended TWRP (jfltecan) for LineageOS 14.1 , which is 3.1.0.
4) Installed TWRP via Odin
5) Booted to TWRP and cleared Dalvik, etc.
6) Installed Optimized LineageOS
7) Went to Developer Options, disabled Root
8) Flashed DisableSuperUser
9) Cleared Dalvik, etc. again
Safety Net Test says "CTS profile match: false" and "Basic Integrity: false"
I tried loading Pokémon GO (one of the few uses of this older device) and get "Unable to authenticate", another clue that SafeNet failed.
Also, I am getting the "Kernel is not Seandroid enforcing" and "Set Warranty Bit: Kernel" messages during bootup.
SELinux is set to "Permissive" and I read setting it to "Enforcing". The kernels found here for this model all seem to set to Permissive. At this point though I'm not sure and I would rather ask for guidance first.
Thanks for any help you may provide!
The bootloader on the sgh-i337m was never locked.
audit13 said:
The bootloader on the sgh-i337m was never locked.
Click to expand...
Click to collapse
Thanks... One thing I don't have to worry about.
I recall that at some point, I did give TWRP full access when prompted. Could this be one of the things that are triggering the Safety Net failures?
I don't know how to revoke the access I granted.
I don't think granting access to TWRP would affect the ROM since TWRP only runs when the phone boots into recovery.
Safetynet may be failing due to a custom ROM that hasn't been signed by Samsung.
You're getting the "not enforcing" because the phone has a custom ROM and recovery.
I'm running J500H. I noticed that when I go into recovery, kernel is not seandroid enforcing shows. Nonetheless, I wiped then flashed lineage os 14.1 NIGHTLY and Gapps 7.1 pico. After reboot, I installed SuperSU from the appstore as it says it is better to download it from there. It shows a popup msg saying "you are not rooted". Any help? I'm really new to this stuff.
Thanks in advance!
Bajao said:
I'm running J500H. I noticed that when I go into recovery, kernel is not seandroid enforcing shows. Nonetheless, I wiped then flashed lineage os 14.1 NIGHTLY and Gapps 7.1 pico. After reboot, I installed SuperSU from the appstore as it says it is better to download it from there. It shows a popup msg saying "you are not rooted". Any help? I'm really new to this stuff.
Thanks in advance!
Click to expand...
Click to collapse
1. its normal if its says "kernel not seandroid enforcing " if you use custom recovery(twrp or cwm for example)
2. you need to root it manually by flashing supersu from custom recovery(download here:
https://download.chainfire.eu/964/supersu/
Thanks! I thought it is not normal.
Done flashing superSU and it now says Im rooted. Thankyou very much :victory:
Thread Closed.