after I root my S4 during booting the following message appears on the screen:
KERNEL IS NOT SEANDROID ENFORCING
SET WARRANTY BIT: KERNEL
Can anyone explain me if this is normal or it's an error message?
The rooting was not completed?
Thank you.
imishte said:
after I root my S4 during booting the following message appears on the screen:
KERNEL IS NOT SEANDROID ENFORCING
SET WARRANTY BIT: KERNEL
Can anyone explain me if this is normal or it's an error message?
The rooting was not completed?
Thank you.
Click to expand...
Click to collapse
Mate .
we need more information , what s4 model you have , what rom you had when rooted, what root method you used??
seem like you rooted but you set the warranty bit, knox kicked in
It's normal. That means you are on a custom kernel.
Lennyz1988 said:
It's normal. That means you are on a custom kernel.
Click to expand...
Click to collapse
Ok man, thank you.
But I have one more question?
I saw that with the same rooting procedure (CF-Auto-Root Android 4.4.2 Package) this message was not displayed on the phone from the example. That was the reason that I started this thread, so I have to understand why my phone is displaying this message
Thank you.
imishte said:
Ok man, thank you.
But I have one more question?
I saw that with the same rooting procedure (CF-Auto-Root Android 4.4.2 Package) this message was not displayed on the phone from the example. That was the reason that I started this thread, so I have to understand why my phone is displaying this message
Thank you.
Click to expand...
Click to collapse
Hi , rooting without setting the warranty bit is possible , like with towelroot , but flashing anything else like a Custom recovery , kernel or rom will kick in knox security
Related
Hey guys
I am currently running with the new bootloader, with the quite famous knox 0x1. I was wondering whether it is possible to downgrade to the previous bootloader, and in that way get rid of the "kernel is not seandroid enforcing" and "Set warranty bit" errors.
I am still a little new with kernels and I don't wont to do anything before I have the right amount of knowledge.
Thanks in advance
/velein
You can't downgrade the bootloader.. I also have knox 0x1 but always remember that you won't have that headache of flashing modems when you change roms
AnaMajhol said:
You can't downgrade the bootloader.. I also have knox 0x1 but always remember that you won't have that headache of flashing basebands when you change roms
Click to expand...
Click to collapse
Okay - thanks for the answer.
One more question: Like i said i am still a newbie (I just install the ROM, and enjoy it!) So what do you mean when you say "flashing modems when you change roms"
I don't know what "baseband" and "modems" are. hehe, sorry if I am to big a newbie.
Thanks
/velein
velein said:
Okay - thanks for the answer.
One more question: Like i said i am still a newbie (I just install the ROM, and enjoy it!) So what do you mean when you say "flashing basebands when you change roms"
I don't know what "baseband" is. hehe, sorry if I am to big a newbie.
Thanks
/velein
Click to expand...
Click to collapse
No worry.. Basebands are the modems that controls all communications for the device and this might help you out:
http://forum.xda-developers.com/showthread.php?t=1574886
Thank you for the quick answer! Helped a lot!
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
How do I stop this from showing when I boot my phone?
synthecypher said:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
How do I stop this from showing when I boot my phone?
Click to expand...
Click to collapse
You can't its triggerd
KingOfDope said:
You can't its triggerd
Click to expand...
Click to collapse
So frustrating it was triggered by ROM Manager.
It asked me if I wanted to disable KNOX as it could cause problems. I didn't realise our want reversible.
Surely if I revert to a ROM using stock kernel if should go away?
synthecypher said:
So frustrating it was triggered by ROM Manager.
It asked me if I wanted to disable KNOX as it could cause problems. I didn't realise our want reversible.
Surely if I revert to a ROM using stock kernel if should go away?
Click to expand...
Click to collapse
unfortunately no KNOX is a hardware (eFuses) thing. Maybe in the future somebody can disable it Look in this thread : LINK they said that Samsung has a tool that can reset it but nobody from the outside got a hand on it
Hi Guys,
Appreciate if you could anyone advise what is appearing top of the screen picture. Is there any possibility to root my device without this message.
Check the picture guys.
Thanks in advance.
http://forum.xda-developers.com/showpost.php?p=64089799&postcount=181
That message clearly shows you've rooted your device. And since its rooted, you must have tripped your knox counter too, making it 0×1 because of which your warranty is now gone. If u want that message to disappear flash the samsung stock firmware which will eventually unroot ur device. But ur knox will remain as it is: 0×1
Shane_Picardo said:
That message clearly shows you've rooted your device. And since its rooted, you must have tripped your knox counter too, making it 0×1 because of which your warranty is now gone. If u want that message to disappear flash the samsung stock firmware which will eventually unroot ur device. But ur knox will remain as it is: 0×1
Click to expand...
Click to collapse
Thanks for the Clarification. I got it!!
mjrifath said:
Thanks for the Clarification. I got it!!
Click to expand...
Click to collapse
Welcome
mjrifath said:
Thanks for the Clarification. I got it!!
Click to expand...
Click to collapse
And if you would have typed seandroid in search all forums on the upper right of the page you would have found About 6,560 results (0.37 seconds)
So I got bored and wanted to root my note 4 N910G.
I went to odin and flashed TWRP and then entered recovery to flash the Emotion Kernel (Emotion-CM-nightly-r21-RC1-SM-N910F.zip)(It is compatible as said on thread) and then flash SuperSU v2.46 .
Now I can't boot up at all and the error above on title. What did i do wrong???
xtherone said:
So I got bored and wanted to root my note 4 N910G.
I went to odin and flashed TWRP and then entered recovery to flash the Emotion Kernel (Emotion-CM-nightly-r21-RC1-SM-N910F.zip)(It is compatible as said on thread) and then flash SuperSU.
Now I can't boot up at all and the error above on title. What did i do wrong???
Click to expand...
Click to collapse
The best way to avoid being bored, is read. Read a lot and you get the solution.
Search and read, before posting, and you will avoid write another useless post.
Rajada said:
The best way to avoid being bored, is read. Read a lot and you get the solution.
Search and read, before posting, and you will avoid write another useless post.
Click to expand...
Click to collapse
i have searched countless number of times, but none of them is helping me as my variant is not same as theirs. And I also followed every instruction they said. Please just this one time. Genuinely
anyone??
xtherone said:
So I got bored and wanted to root my note 4 N910G.
I went to odin and flashed TWRP and then entered recovery to flash the Emotion Kernel (Emotion-CM-nightly-r21-RC1-SM-N910F.zip)(It is compatible as said on thread) and then flash SuperSU v2.46 .
Now I can't boot up at all and the error above on title. What did i do wrong???
Click to expand...
Click to collapse
THE ONLY way to have root @ android 5.1.1 SO FAR is to "screw" with kernel ... That's why there are RED LETTERS saying KERNEL is not seandroid enforcing ... IT WILL WRITE like that on EVERY CUSTOM kernel ... That means on 90% of the rooted/custom ROMS that are avaliable ... So, your problem is not in those big bad red letters, it's something else ... Almost EVERY thread about custom roms has that mentioned, there even were a couple of threads in general section ... Just try to search a bit, pretty please?
And FYI I just did a google search for "Kernel is not seandroid enforcing Note 4" and got the answer on the first page, so ...
Doomhamma said:
THE ONLY way to have root @ android 5.1.1 SO FAR is to "screw" with kernel ... That's why there are RED LETTERS saying KERNEL is not seandroid enforcing ... IT WILL WRITE like that on EVERY CUSTOM kernel ... That means on 90% of the rooted/custom ROMS that are avaliable ... So, your problem is not in those big bad red letters, it's something else ... Almost EVERY thread about custom roms has that mentioned, there even were a couple of threads in general section ... Just try to search a bit, pretty please?
And FYI I just did a google search for "Kernel is not seandroid enforcing Note 4" and got the answer on the first page, so ...
Click to expand...
Click to collapse
But i didn't flash any custom roms. All I did was to boot up
xtherone said:
But i didn't flash any custom roms. All I did was to boot up
Click to expand...
Click to collapse
You wrote : "So I got bored and wanted to root my note 4 N910G.
I went to odin and flashed TWRP and then entered recovery to flash the Emotion Kernel (Emotion-CM-nightly-r21-RC1-SM-N910F.zip)(It is compatible as said on thread) and then flash SuperSU v2.46 .
Now I can't boot up at all and the error above on title. What did i do wrong???"
From that post I conducted that you flashed a kernel right? Well that kernel had root access and that's why You see that message that kernel is not seandroid enforcing.
Doomhamma said:
You wrote : "So I got bored and wanted to root my note 4 N910G.
I went to odin and flashed TWRP and then entered recovery to flash the Emotion Kernel (Emotion-CM-nightly-r21-RC1-SM-N910F.zip)(It is compatible as said on thread) and then flash SuperSU v2.46 .
Now I can't boot up at all and the error above on title. What did i do wrong???"
From that post I conducted that you flashed a kernel right? Well that kernel had root access and that's why You see that message that kernel is not seandroid enforcing.
Click to expand...
Click to collapse
But my device did not boot up. However, thanks for helping me! I figured it out by flashing a bootloader via odin and then flashing a custom rom instead of booting into the stock rom :good:
Hi xtherone,
"I figured it out by flashing a bootloader via odin and then flashing a custom rom instead of booting into the stock rom"
I've got a similar problem with a N910C, just wondered if you could point me in the right direction - I'm not sure where I can get the correct version of Odin, bootloader or a properly compatible ROM
Any help appreciated...
I am on n910u and I am also looking for a bootloader for 5.1.1 I havent been able to find one yet.
Hi All
I have SM-E700H android 5.1.1
I tried to root 3 methods like
Kingroot, cfautoroot, supersu.zip
But I faced one common warning
In every methods that is
"set warranty bit : kernel"
What is this? But I don't want this
Type of warnings like in android 4.4.4
With cfautoroot.
Anybody Help me????
Thanks
pkdubai20 said:
Hi All
I have SM-E700H android 5.1.1
I tried to root 3 methods like
Kingroot, cfautoroot, supersu.zip
But I faced one common warning
In every methods that is
"set warranty bit : kernel"
What is this? But I don't want this
Type of warnings like in android 4.4.4
With cfautoroot.
Anybody Help me????
Thanks
Click to expand...
Click to collapse
It is because samsung has implemented security that doesnt allow to modify the system. Cfroot by chainfire modifies th boot.img to allow root with system less root. Because the kernel is modified in the process thus the message Set warranty bit kernel. kingroot does the same. In kitkat there was no protection like that.
Its not of a bothering message for exchange of root.
nepalbiraj said:
It is because samsung has implemented security that doesnt allow to modify the system. Cfroot by chainfire modifies th boot.img to allow root with system less root. Because the kernel is modified in the process thus the message Set warranty bit kernel. kingroot does the same. In kitkat there was no protection like that.
Its not of a bothering message for exchange of root.
Click to expand...
Click to collapse
nepalbiraj you mean everyone who
have (SM-E700H android 5.1.1) this
device and root, all are getting same
warning like this?
pkdubai20 said:
nepalbiraj you mean everyone who
have (SM-E700H android 5.1.1) this
device and root, all are getting same
warning like this?
Click to expand...
Click to collapse
yup thats right. I am too getting the same warning everytime.
nepalbiraj said:
yup thats right. I am too getting the same warning everytime.
Click to expand...
Click to collapse
It not defect longer to device?
pkdubai20 said:
It not defect longer to device?
Click to expand...
Click to collapse
No It doesnt defect and has no effect on device. Kernel or recovery Not signed by samsung results the warning.
Just ignore it.It doesnot do anything.
you developers also can't
fix it? if can try to fix it
as soon as possible.
we hope.....
Thanks