kernel is not seandroid enforcing? (2024)

I just installed lineage os 14.1. And every time I boot up my tablet, this message is there. Whether I power it on, boot into recovery, or restart. I've searched for a solution, but people say I need to go back to stock. And I don't want to do that because my tablet works....flawlessly.

Is it suppose to say it? And is there a way to get rid of this message without completely going back to stock?

SM-T810 here.

jshamlet said:

Learn to ignore it? It doesn't actually hurt anything, so if you are otherwise happy, leave it alone.

Click to expand...

Click to collapse

I am ignoring it. I'm not panicking here. Just asking if it is supposed to be there. I guess it is.

sal82 said:

I am ignoring it. I'm not panicking here. Just asking if it is supposed to be there. I guess it is.

Click to expand...

Click to collapse

It could be worse. My old HTC One M8 put up a paragraph of legalese on every boot, including implying my phone was still the property of HTC, because I was running a custom kernel/recovery. It was clearly meant to only show up on true development devices, but anything other than stock triggered it.

sal82 said:

I just installed lineage os 14.1. And every time I boot up my tablet, this message is there. Whether I power it on, boot into recovery, or restart. I've searched for a solution, but people say I need to go back to stock. And I don't want to do that because my tablet works....flawlessly.

Is it suppose to say it? And is there a way to get rid of this message without completely going back to stock?

SM-T810 here.

Click to expand...

Click to collapse

I think that's normal. I had a Tab S 8.4 with LOS 14.1 and had the same message. Somewhere in the Lineage thread for that model explained it but I've forgotten the explanation.

Here is what I found on Google:

If you see 'Recovery is is not Seandroid Enforcing' or 'Kernel is not Seandroid Enforcing', it probably means that you have installed a wrong CWM/TWRP recovery or wrong custom ROM on your phone or try to root the phone with a file that is incompatible with your current firmware. For example, you installed a 4.3 TWRP recovery on an Android 4.4 phone; you rooted your phone on Android 5.1 with a CF-Auto-Root file for Android 5.0.2.

Click to expand...

Click to collapse

See Also

Fix Kernel / Recovery is Not Seandroid Enforcing Without Deleting Data

And although it`s usually us amateurs fault it can also happen, when you install a custom ROM or Touchwiz that is still in early development.

If anyone could elaborate on what it actually means besides the obvious, meaning bring light on the technical aspect in any way, I'd be interested.

McFex said:

Here is what I found on Google:

And although it`s usually us amateurs fault it can also happen, when you install a custom ROM or Touchwiz that is still in early development.

If anyone could elaborate on what it actually means besides the obvious, meaning bring light on the technical aspect in any way, I'd be interested.

Click to expand...

Click to collapse

I saw that too. And it's nonsense. TWRP and LOS work flawlessly. So how are they the wrong ones?

McFex said:

Here is what I found on Google:

And although it`s usually us amateurs fault it can also happen, when you install a custom ROM or Touchwiz that is still in early development.

If anyone could elaborate on what it actually means besides the obvious, meaning bring light on the technical aspect in any way, I'd be interested.

Click to expand...

Click to collapse

The message is harmless and only means an unsigned boot or recovery image is being used.
Samsung sign all their software with a key.
Without this key any unsigned binary installed will produce this message unless the binary is patched.

ashyx said:

The message is harmless and only means an unsigned boot or recovery image is being used.
Samsung sign all their software with a key.
Without this key any unsigned binary installed will produce this message unless the binary is patched.

Click to expand...

Click to collapse

Thank you ashyx, that's exactly what I meant with explaining the technical aspect.
As my Tab also worked flawlessly, when I had the message, I had a feeling it might be something like that.

So phone is safe to use with 14.1?

Phone is rebooting continuously , heating after singinging in Google,
It will happen like this since its not compatible. Have any one found this rebooting issue after Google signing?