Database Info

[Q] Kernel is not seandroid enforcing (CM12)

I just flashed the latest CM12 and it's great. Also installed TWRP.
The only issue is that now when I boot my P900 shows in red: Kernel is not seandroid enforcing.
Is this a problem and, how do I get rid of it?

Agrajag27 said:
I just flashed the latest CM12 and it's great. Also installed TWRP.
The only issue is that now when I boot my P900 shows in red: Kernel is not seandroid enforcing.
Is this a problem and, how do I get rid of it?
Click to expand...
Click to collapse
your bootloader detects that, so there is no way to get rid of it.
my note 4 does this but I have actually never seen it on my P900, could you give more details on your exact model, rom, and kernel? I'm curious.
one way around that, I think, would be a kernel that is enforcing at boot, then use a script or an app to toggle it back to permissive (if necessary for your purposes)
edit: oops I see now -- CM 12, but still.. are you using the lollipop bootloader from the official update?

Hmmm.... I just rooted my Note Pro last night, stock rom with TWRP (latest). And though it boots up fine otherwise, I'm also getting the "Not SEAndroid enforcing" message. Would like that gone. And it is interesting that CM12 is having the same issue, because I was beginning to think about flashing it and ditching stock Lollipop.
Specifics: I used Odin 3.10 from a Windows 7 laptop for my initial boot flash of the CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 file to the tablet. No errors were reported. I also flashed TWRP 2.8.7 that way. Again, no errors. There was a beta version of SuperSU (2.49) but I didn't install that. Think I'll try it next... and hope for the best. I did install SuperSU Pro (2.46) once I'd booted the tablet, but maybe that's not available on boot?

Sterist said:
could you give more details on your exact model, rom, and kernel? I'm curious.
Click to expand...
Click to collapse
SM-P900 like you.
CyanogenMod Version: 12.1-20150707-UNOFFICIAL-v1awifi
Android version 5.1.1
Kernel version: 3.4.104-g7e89e2e
[email protected] #1
Tue Jul 7 19:20:11 MSK 2015

Agrajag27 said:
SM-P900 like you.
CyanogenMod Version: 12.1-20150707-UNOFFICIAL-v1awifi
Android version 5.1.1
Kernel version: 3.4.104-g7e89e2e
[email protected] #1
Tue Jul 7 19:20:11 MSK 2015
Click to expand...
Click to collapse
but did you at some point OTA or odin to Samsung lollipop before CM12.1?

Sterist said:
but did you at some point OTA or odin to Samsung lollipop before CM12.1?
Click to expand...
Click to collapse
Yes. I OTA 5.0.2.
I guess the big questions are:
1. Is there a fix that doesn't involve jumping back to KitKat?
2. Is having this issue in any way bad other than seeing that message on boot as everything else seems to be working.

Agrajag27 said:
Yes. I OTA 5.0.2.
I guess the big questions are:
1. Is there a fix that doesn't involve jumping back to KitKat?
2. Is having this issue in any way bad other than seeing that message on boot as everything else seems to be working.
Click to expand...
Click to collapse
I don't think there would be a way to go back to kitkat, even if you wanted to, after having installed the lollipop bootloader (happens when you OTA or Odin to stock lollipop)
to the user it's no problem at all -- it's just a visual notification to stores when you take the device back that it's been customized / modded, and voids the knox warrantee hence "Set warrantee bit: kernel"
knox, despite popular belief, is just a form of security and productive software for corporations to rely on when giving their employees a "work phone" to use, so they know that any potentially sensitive corporate information is safe from the security risks of rooting (though virtually never exploited, rest assured)
that's the most relevant answer I can give you, without repeating what I explained in my previous post *hint* lol

Slightly confused about something I'm seeing. The error is that it's NOT enforcing, but Settings, About Tablet says it IS enforcing.
Also, you mention setting to Permissive with an app (which I've found) but that sounds like it won't be enforcing either and thus we'll still have the message.

Agrajag27 said:
Slightly confused about something I'm seeing. The error is that it's NOT enforcing, but Settings, About Tablet says it IS enforcing.
Also, you mention setting to Permissive with an app (which I've found) but that sounds like it won't be enforcing either and thus we'll still have the message.
Click to expand...
Click to collapse
the display at boot is not an error, just a notification of sorts.
the only thing I can think of is the CM maintainer may have compiled the kernel to boot as permissive and switch back via script for compatibility.
I have seen some roms that do this. not many, nor recently. I wouldn't worry about it though, especially since it's a Wi-Fi device that doesn't have any reason to visit a carrier store.
also note that the notification will show when booting a permissive recovery kernel -- these notifications are not permanent nor need to be "cleared" or "reset" they just inform the user (or technician) of the S.E.A. mode of the respective kernel at the time of boot.

Thanks. I can live with that. I'm a bit OCD and an old QA professional so it'll give me pause every time I reboot and see it, but I'll get over it. <grin>
Otherwise, I have to say, the tablet is working better than EVER with CM 12.x. Apps that caused crashes no longer do. Bluetooth keyboard works again. It's faster. I have only a single bug (the running apps list sometimes has graphic issues).

So im assuming i just messed up myself here

I got this s6 back in march or april and it was on 5.0.2 and well now that iv've updated to the OTAS 5.1.1 OFE i was curious about root and i continued with a thread about rooting it and etc
( i kinda regret that now, i shouldve stayed on 5.0.2)
but the main reason i rooted was to recover files and welli did but i installed dr fone on my computer it asked for my phones root permissions so i went ahead and rooted it but after a bit i noticed it started to freeze my phone and after a bit it just stopped working.
i turn it on and restart it i see a blue led cycling and i see the sprint spark screen but it does nothing from there.
and so i stupidly went to to stock recovery, wiped cache, and factory resetting it and now idk what to do
there isnt an OFE stock tar yet so i cant fix this on my own, im just thinking if i flash twrp right now and then flash a custom rom will that work?? for my OFE build

am i able to or should i just download the stock tar 5.0.2 to reflash it or will that just basically brick me completely??
also i did have insurance for this and i thnink i just blew that one too :/

ive noticed mine said this
G920PVPU2BOFE
and not G920PVPU2BOF7
so does that mean im able to use the stock firmware from the website and reflash it or like what do i do...

SO what i did countless of researching
i ended up having the
custom binary blocked by FRP lock, by forgetting to unlock oem before updating the Twisted Projects SuperSu or User since it asked me to updated i ovbiously just went ahead of myself and that happened thus into this Boot Loop Soft
and im flashing with ODIN the stock 5.1.1 OF7 tar its surprisingly working. ( i was originally on the OFE OTA tho.)
unlike the Twisted Project custom roms, kernel and or twrp setup, i couldnt boot into the twrp or even past the android screen, and well the only option i had was just Download Mode.
And this basically saved me.

Very Informative

Soft brick..redux

Having soft brick issues and need some guidance
History: Early 2014 purchased used sch 1535 used which was completely stock. Rooted with Saferoot and flashed a stock (?) debloated 4.3 ROM, which I thought was getting me around Knox, etc. However, Download mode shows Current Binary = Samsung Official so I don't really know what that means with regard to my ROM.
Recently, I've had performance issues/crash so looked into upgrading ROM. Got caught up in an XDA developer thread about how to downgrade to 4.1 to defeat 4.3 lock bootloader issues and though it flashed, ended up in a boot loop. Was at first still able to boot into recovery but attempts to reflash w/ stock recovery tar and higher version 4.4 left me without recovery, although I still can get to ODIN (-volume, home, power). Am now getting the yellow triangle ("unauthorized software) when I attempt reboot (power only) or boot into recovery ( +volume, home, power) .
Have tried LOTS of debrick threads over the last 12 hours trying to figure this out and in addition to stock ROMs mentioned previously, have attempted to flash bootchain, pit file, etc. One of the things I'm wondering about is whether I need to flash a non-stock ROM since I am rooted. The splash screen on bootup still shows the custom unlock icon and in Download mode I see that the System Status = Custom
Any thoughts on what I need to do next would be greatly appreciated. Will be glad to post more information on what I've tried but trying not to make this much longer. Thx!

Samsung GS7 Extreme Battery Drain After Root!

Hello,
So I tried rooting the GS7 recently. It was successful but I kept getting an 'Unauthorized Actions' error. I tried everything I could to get the warning to go away but couldn't resolve it. I've unrooted and have reverted back to stock and did a factory reset. However, now I'm seeing that my battery is draining faster than it charges. I booted into recovery mode and after the "downloading" screen I see an android lying down with a yellow exclamation point over his head. It goes to recovery and at the bottom it says supported APIs: 3 which I've never noticed before. I'm in way over my head and really regret trying to root. I just wanted to access my hosts file so I could block some websites. I'm not sure what to do now and am seeking some advice. I just want my old phone back. =' (
Thanks!

This happened to me after rooting, i experienced battery drain when my galaxy s7 G930F was idle, about 2%-5% per hour drain, there doesn't seem to be a wake lock as I've checked all my apps. what i would recommend doing is make a backup, check your device baseband version and remember it, then through recovery format data of your entire phone, then use odin to install a stock rom from sammobile (it should be the one that matches your baseband version).
if you have trouble just search in google for "install stock rom s7 odin" check if there is a tutorial for your model of galaxy s7!

Finally got my S6 rooted, but now can't get into recovery mode... and other issues

So I'm no developer, but I'm pretty good at following instructions and figuring things out by piecing information together. I have a galaxy s6 model sm-g920r7 on 6.0.1 originally bought from Ntelos, which from what I've read in various places, is the same model number and hardware as the c spire version. I've spent nearly 2 years trying to get this thing rooted, and finally managed to get that done somewhat successfully. The way I did it was by using the cf autoroot for the sprint version sm-g920p, because I figured since sprint bought out Ntelos, maybe the sprint version would be compatible.
Well, It went smoothly, and root checker says I'm rooted. But I can't get a successful twrp install. I've tried the twrp app, and I've tried flashing with odin. the twrp app gives me an error when I try to install, and odin just gets stuck and won't finish. Trying to get into recovery mode, it just goes to the samsung load screen with red words at the top saying recovery is not seandroid enforcing. I'm assuming that it has something to do with the SELinux being set to enforcing rather than permissive, but I can't find a way to fix that either. I've tried changing it to permissive with terminal emulator, and that doesn't do anything.
I want to install a custom rom, so I'm trying everything i can find to get it working as it should but there's so little information out there about my phone model. I've dragged this out for way too long to give up now and get a different model. Hell, at this point, it's really just about solving the puzzle anyway, since I upgraded to the s7 edge. If anyone has a clue what I can do to solve any of these issues, I'd be greatly appreciative.

Update: Found this version of twrp, flashed with odin, and now I can get into recover. But it still gives the "recovery not seandroid enforcing" in red letters above the samsung logo before going into twrp recovery mode. So I'm not even sure what's going on with that.