Hello guys, I've read about knox and now I get how it works and all, warranty isn't an issue for me (long story) so now I have the new bootloader flagged 0x1, now my question is whenever I boot into recovery or into OS I'm greeted with "set warranty bit : recovery/kernel" and "recover/kernel is not seandroid enforcing", I also kind of understand that this is related to knox bootloader but is it something I should worry about? Will flashing different roms/kernels now that I'm on the new bootloader mess up anything other than the already flagged 0x1? Thanks.
reckoner_85 said:
Hello guys, I've read about knox and now I get how it works and all, warranty isn't an issue for me (long story) so now I have the new bootloader flagged 0x1, now my question is whenever I boot into recovery or into OS I'm greeted with "set warranty bit : recovery/kernel" and "recover/kernel is not seandroid enforcing", I also kind of understand that this is related to knox bootloader but is it something I should worry about? Will flashing different roms/kernels now that I'm on the new bootloader mess up anything other than the already flagged 0x1? Thanks.
Click to expand...
Click to collapse
No, it's nothing to worry about at all, just ignore it
Or when booting to recovery go a bit cross eyed and enjoy a funky rainbow effect, it's amazing
Obagleyfreer said:
No, it's nothing to worry about at all, just ignore it
Or when booting to recovery go a bit cross eyed and enjoy a funky rainbow effect, it's amazing
Click to expand...
Click to collapse
haha I will definitely try that.
reckoner_85 said:
haha I will definitely try that.
Click to expand...
Click to collapse
how do u bypass the error? I want to use 4.4
Obagleyfreer said:
No, it's nothing to worry about at all, just ignore it
Or when booting to recovery go a bit cross eyed and enjoy a funky rainbow effect, it's amazing
Click to expand...
Click to collapse
i kinda have the same issue, only i dont have video/audio, and wifi....and ideas?
Help
Hy i have big problem
I try to root Galaxy s4 and all is fine but when i turn on phone he say
"kernel is not seandroid enforcing"
and this is all
Please help me how to fix this
Thanks
martin93612 said:
Hy i have big problem
I try to root Galaxy s4 and all is fine but when i turn on phone he say
"kernel is not seandroid enforcing"
and this is all
Please help me how to fix this
Thanks
Click to expand...
Click to collapse
This appears coz u changed the STOCK kernel. The unique way to solve this is installing STOCK ROM again :good:
Can you send me where i can fnde to dowload stock ROM and i can't enter in CWM to instal can this instal from ODIN?
Thank you
martin93612 said:
Can you send me where i can fnde to dowload stock ROM and i can't enter in CWM to instal can this instal from ODIN?
Thank you
Click to expand...
Click to collapse
Check the Back to Stock link in my signature! Any queries direct to that thread:good:
Thanks finaly my phone working
Thank you :victory:
Obagleyfreer said:
No, it's nothing to worry about at all, just ignore it
Or when booting to recovery go a bit cross eyed and enjoy a funky rainbow effect, it's amazing
Click to expand...
Click to collapse
Laughed loud. Just wanted to let you know.
Please Help! Ive been searching all day yesterday to fix my phone
So i wanted to be updated so i downloaded mf9 and mja and all the kernels or whatever and installed them and was on stock non rooted rom for a while, yesterday i wanted to install sacs custom rom so i downloaded the newest one and flashed via twrp, but now all that happens is i get a message saying "Kernel is not seandroid enforcing" in red "Set warrenty Bit: Kernel" in yellow, I cannot flash anything via odin except philz recovery so i have that on there but i tried to install the stock firmware through odin and everything fails. I even changed usb cords, took out the .md5 extension, plugged the usb cord directly to the motherboard instead of using the front usb which that allowed me to flash philz recovery but i just want a working phone, no rom is working and I cant install any roms please help i need my phone back! Thanks, Chris
Same here :/
chriscolby7 said:
So i wanted to be updated so i downloaded mf9 and mja and all the kernels or whatever and installed them and was on stock non rooted rom for a while, yesterday i wanted to install sacs custom rom so i downloaded the newest one and flashed via twrp, but now all that happens is i get a message saying "Kernel is not seandroid enforcing" in red "Set warrenty Bit: Kernel" in yellow, I cannot flash anything via odin except philz recovery so i have that on there but i tried to install the stock firmware through odin and everything fails. I even changed usb cords, took out the .md5 extension, plugged the usb cord directly to the motherboard instead of using the front usb which that allowed me to flash philz recovery but i just want a working phone, no rom is working and I cant install any roms please help i need my phone back! Thanks, Chris
Click to expand...
Click to collapse
I am having the same issue as you Chris, I'm on the sprint galaxy s4 and i get those same errors and get stuck on a black screen with the blue led illuminated on the top, I can access recovery and download mode. I hope we get some help soon
Stock
Joku1981 said:
This appears coz u changed the STOCK kernel. The unique way to solve this is installing STOCK ROM again :good:
Click to expand...
Click to collapse
But I can't go to recovery/download mode. How can I installing STOCK ROM?
Is there a way to bypass the error?
same problem here. gets stuck at the samsung galaxy s4 spash screen
Obagleyfreer said:
No, it's nothing to worry about at all, just ignore it
Or when booting to recovery go a bit cross eyed and enjoy a funky rainbow effect, it's amazing
Click to expand...
Click to collapse
but gamekiller not working fine..
Here is the Solution
reckoner_85 said:
Hello guys, I've read about knox and now I get how it works and all, warranty isn't an issue for me (long story) so now I have the new bootloader flagged 0x1, now my question is whenever I boot into recovery or into OS I'm greeted with "set warranty bit : recovery/kernel" and "recover/kernel is not seandroid enforcing", I also kind of understand that this is related to knox bootloader but is it something I should worry about? Will flashing different roms/kernels now that I'm on the new bootloader mess up anything other than the already flagged 0x1? Thanks.
Click to expand...
Click to collapse
All Right I have the solution for you! I was lucky enough to find someone that knew how to fix this (Damageless) so here is what you need to do.
-Take out the battery and disconnect from computer
-Put battery back in and hold down Vol(down) and home key, then hold power button until it vibrates. Release only the power button after it vibrates.
-You should now be in the download mode, click Vol(up) to continue.
-Download Odin here: odindownload .com
-Download stock ROM here: (dont open click save) sammobile .com and (yes you have to create an account I'm sorry) search for your model number, ex. SM-N900t for tmobile note 3
-install Odin
-check the PDA box not phone and click PDA
-find the stock ROM in your downloads and select that one.
-hit Start and you should be back to normal
It will erase everything you had on your phone which sucks I know but at least your phone works! Good luck! Hope this helps!
Wroclaw7
i have same problem them flash carbon rom and works...
martin93612 said:
Can you send me where i can fnde to dowload stock ROM and i can't enter in CWM to instal can this instal from ODIN?
Thank you
Click to expand...
Click to collapse
You can get all stock firmwares from SamMobile : http://www.sammobile.com/firmwares/
Let me know if you need help with the flashing process.
THANK YOU
THANK YOU THANK YOU I found this post and it restored my phone back to stock!!!!
the only thing I can add to this is use the original cable that came with the phone I was using an aftermarket one and was getting error after error .
Hi Guys
Could really use some help here, thought it was about time that I rooted my Note 3, I am using a SM-n9005 and was on 4.3 to start.
I followed some instructions using Odin and CF-autoroot, all went well even had a pass! in the Odin screen but now I am stuck on the loading screen with the following error messages in the left hand corner:
Recovery booting....(in blue)
Recovery is not seandroid enforcing (in red)
Set warranty bit : recovery (in yellow)
Can anyone shed some light on this ? what have I done wrong here and how can I fix it ?
Thank you
colobos said:
Hi Guys
Could really use some help here, thought it was about time that I rooted my Note 3, I am using a SM-n9005 and was on 4.3 to start.
I followed some instructions using Odin and CF-autoroot, all went well even had a pass! in the Odin screen but now I am stuck on the loading screen with the following error messages in the left hand corner:
Recovery booting....(in blue)
Recovery is not seandroid enforcing (in red)
Set warranty bit : recovery (in yellow)
Can anyone shed some light on this ? what have I done wrong here and how can I fix it ?
Thank you
Click to expand...
Click to collapse
I think you used wrong cf autoroot you might downloaded the 4.4 kitkat version
meawww said:
I think you used wrong cf autoroot you might downloaded the 4.4 kitkat version
Click to expand...
Click to collapse
Thank you I managed to figure it out and you was right I was being a bit of a moron .....
to unroot phone for a friends galaxy s4 i need to download the stock provider files for the phone but i have no idea what the original provider was.
Is there a way to find out what the stock provider was and can i install any provider firmware ?
akatheproducer said:
to unroot phone for a friends galaxy s4 i need to download the stock provider files for the phone but i have no idea what the original provider was.
Is there a way to find out what the stock provider was and can i install any provider firmware ?
Click to expand...
Click to collapse
This is easy if you know the CSC. Only:
1. Install Kies (android 4.2.2/ android 4.3) or Kies 3 (android 4.4.2). Conect ur friend's phone to the pc.
2. Look for the CSC (Pic 1 attached).
3. You can go to Sammobile.com and download the latest firmware for the provider of your friend.
4. Flash it through ODIN and enjoy :highfive:
but it seems i got bigger fish to fry , i had asked someone here if my kernel # was stock and they said yes however now after i downloaded the carrier files and installed the phone is tuck on boot Samsung Galaxy S4 screen . there is a message in the top left corner that says
KERNEL IS NOT SEANDROID ENFORCING
SET WARRANTY BIT:KERNEL
akatheproducer said:
but it seems i got bigger fish to fry , i had asked someone here if my kernel # was stock and they said yes however now after i downloaded the carrier files and installed the phone is tuck on boot Samsung Galaxy S4 screen . there is a message in the top left corner that says
KERNEL IS NOT SEANDROID ENFORCING
SET WARRANTY BIT:KERNEL
Click to expand...
Click to collapse
Well that someone is @AL_IRAQI
Did you try a data wipe after that? No? Try that first on stock recovery.
And kernel not seandroid enforcing is not an issue. Ignore that and data wipe.
"If someone helps, never forget to hit thanks ?"
DeepankarS said:
Well that someone is @AL_IRAQI
Did you try a data wipe after that? No? Try that first on stock recovery.
And kernel not seandroid enforcing is not an issue. Ignore that and data wipe.
"If someone helps, never forget to hit thanks ?"
Click to expand...
Click to collapse
i keep doing data wipe and cache partition wipe I've tried them all and the phone always comes back stuck at the same screen
akatheproducer said:
i keep doing data wipe and cache partition wipe I've tried them all and the phone always comes back stuck at the same screen
Click to expand...
Click to collapse
Check your original thread.
"If someone helps, never forget to hit thanks ?"
Hello guys,
My phone KingRoot root after, Kernel is SeAndroid not enforcing error message and Recovery is not SeAndroid not enforcing.
How to fix via easy steps
Would it hurt my device?
you can't fix it, your warranty is now void but it probably was anyway... it's Knox in your bootloader that detects that your kernel and recovery are not enforcing the security policy.
there's a whole huge topic in the s4 general forum all about it...
3mel said:
you can't fix it, your warranty is now void but it probably was anyway... it's Knox in your bootloader that detects that your kernel and recovery are not enforcing the security policy.
there's a whole huge topic in the s4 general forum all about it...
Click to expand...
Click to collapse
Would it hurt my device?
Thank.
Device is stable running. Only booting text showing.
karansa said:
Would it hurt my device?
Thank.
Click to expand...
Click to collapse
No. That message is completely normal after the device has been rooted.
GDReaper said:
No. That message is completely normal after the device has been rooted.
Click to expand...
Click to collapse
Nice, thanks.
Hi All,I tried to root my J5 with CFautoroot it showed passed ,screenshot is attached (http://prnt.sc/dbj19y) but what phone does is show two lines after turning on
Recovery is not Seandroid Enforcing(in red)
(and)
set warranty bit : recovery
any help would be much appreciated
aliashraf4141 said:
Hi All,I tried to root my J5 with CFautoroot it showed passed ,screenshot is attached (http://prnt.sc/dbj19y) but what phone does is show two lines after turning on
Recovery is not Seandroid Enforcing(in red)
(and)
set warranty bit : recovery
any help would be much appreciated
Click to expand...
Click to collapse
@aliashraf4141
Because u r using custom recovery
aliashraf4141 said:
Hi All,I tried to root my J5 with CFautoroot it showed passed ,screenshot is attached (http://prnt.sc/dbj19y) but what phone does is show two lines after turning on
Recovery is not Seandroid Enforcing(in red)
(and)
set warranty bit : recovery
any help would be much appreciated
Click to expand...
Click to collapse
Thats very normal. Custom recoveries will provoke such notifications. If u flash stock firmware or stock recovery that message will disappear
Can you please guide me through steps please
aarushmukesh said:
@aliashraf4141
Because u r using custom recovery
Click to expand...
Click to collapse
How to solve this,any steps,your help would be much appreciated
aliashraf4141 said:
How to solve this,any steps,your help would be much appreciated
Click to expand...
Click to collapse
May i know why u want to solve that? If u dont want a custom Rom then flash official firmware and then root with Kingroot:good: . Lol i dont think those 2 lines should bother u
KingRaheel said:
May i know why u want to solve that? If u dont want a custom Rom then flash official firmware and then root with Kingroot:good: . Lol i dont think those 2 lines should bother u
Click to expand...
Click to collapse
They have no need to bother you, they only show up for 2 seconds whilst booting.
As kingRaheel has said that's what you get with these custom ROMs
John