Hi i've been using custom roms ( CM & SOKP ) and both gave me this problem on boot ( kernel is not seandroid enforcing - set warranty bit kernel ) but the phone works fine boots up with zero problem, is there a problem in the kernel ? i flashed recently [EMOTION KERNEL] used all his tweaks with no problem ( tap2wake .. gamma .. ) but didn't correct the message in boot any ideas ? try another custom kernel ?? Thanks
kherboucha said:
Hi i've been using custom roms ( CM & SOKP ) and both gave me this problem on boot ( kernel is not seandroid enforcing - set warranty bit kernel ) but the phone works fine boots up with zero problem, is there a problem in the kernel ? i flashed recently [EMOTION KERNEL] used all his tweaks with no problem ( tap2wake .. gamma .. ) but didn't correct the message in boot any ideas ? try another custom kernel ?? Thanks
Click to expand...
Click to collapse
Custom roms ( CM & SOKP ) = kernel is not seandroid enforcing - set warranty bit kernel
Custom recovery (CWM & TWRP) =recovery is not seandroid enforcing
d4rkkn16ht said:
Custom roms ( CM & SOKP ) = kernel is not seandroid enforcing - set warranty bit kernel
Custom recovery (CWM & TWRP) =recovery is not seandroid enforcing
Click to expand...
Click to collapse
yeah i know but for exemple yesterday i flashed cm11 on a i9000 worked fine and no message on boot, maybe the kernel associated with note 4 roms isn't completely developed yet ?
It's 5.1.1 feature (annoyance)
On 6 November 2013 the CyanogenMod team started pushing the code of CyanogenMod 11, based on Android 4.4 KitKat, to GitHub.
Click to expand...
Click to collapse
Related
Hi
I was on NA6 Kitkat (Rooted with CF auto root), and wanted to install V37 Temasek.
So, i installed latest CWM 6.0.4.6
I flashed V37 + Gapps (with all wipes done) = Bootloop at start
"Kernel is not blablabla enforcing" again & again...
Had to reflash stock NA6 to got a working N9005...
So, impossible to flash non TW roms for the moment ?
If this thread can avoid people to waste time like i did... :good:
luminouche said:
Hi
I was on NA6 Kitkat (Rooted with CF auto root), and wanted to install V37 Temasek.
So, i installed latest CWM 6.0.4.6
I flashed V37 + Gapps (with all wipes done) = Bootloop at start
"Kernel is not blablabla enforcing" again & again...
Had to reflash stock NA6 to got a working N9005...
So, impossible to flash non TW roms for the moment ?
If this thread can avoid people to waste time like i did... :good:
Click to expand...
Click to collapse
Hey i having a similar problem but is a but different i can boot in to CWM and install roms like Sweet ROm TW based but when i boot to android
it just goes to the normal stock firmware
But when i flash any AOSP based roms i just get stuck in bootloops like you do
Once on kit kat official you cannot flash cm 4.4.2 until bootloader fix press thanks if this helps
Sent from my SM-N9005 using XDA Premium HD app
Galaxy note 3 sm n900 vn rom installation
I currently have a galaxy note 3 sm n900 and am trying to install vn rom and it is stuck at 0% is there anything i can do. (been at 0% for a whole day):crying:
Hello All.
As the questions states, I am looking for a stock kernel for the international S4 (I9-500) running Android OS 4.4.2 which changes the SELinux properly from enforcing to permissive.
Is there a kernel out there for this S4 version that does what I am needing? Basically, because on 4.4.2 SELinux is set to enforcing and because programs like SELinuxModeChanger do not work I am thinking a kernel may solve the issue?
My build number is XXUFNE7 if that helps.
Many thanks.
ianwuk
Hi guys
I installed a ported rom of s5 of @g00h with lean kernel 3.7 in my boot i see this Kernel is not seandroid enforcing set warranty bit
And when booting to recovery i see
Recovery is not seandroid enforcing
But every thing is working fine and i am asking is that dangerous for the phone or will brick it because i read on the net that you need to change kernel or something please help my recovery is philz touch 6 and i have a SM N9005 THANK YOU VERY MUCH
abdel310 said:
Hi guys
I installed...
Click to expand...
Click to collapse
Your first custom rom ?
But you really need to sharpen your searching skills.
2 minutes of searching would give you that this writing is normal when you install a custom kernel or custom recovery.
Sent from my N9005
Yes my first custom rom thanks for the answer
Hi everyone, anyone knows how can I use V4A on Lollipop? Tutorials for other phones say that SeLinux needs to be Permissive, but on S5 it can't be switched to because of Knox. BUT I remember that on KitKat I had SeLinux Enforcing and I was able to use V4A! Please help!!!
obrobrio2000 said:
Hi everyone, anyone knows how can I use V4A on Lollipop? Tutorials for other phones say that SeLinux needs to be Permissive, but on S5 it can't be switched to because of Knox. BUT I remember that on KitKat I had SeLinux Enforcing and I was able to use V4A! Please help!!!
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?p=58671088
SM-G900W8, 0x1
A recovered flashaholic since Aliance Rom 5.5
Same problem, i m on alexndr BOE6 rom
Solved: install Boeffla Kernel, set SEAndroid to permissive in Boeffla Config app and reboot. After this, go to Application Manager in settings, go to All tab, search SoundAlive, tap on it and then on Disable, and then install V4A and reboot!
Hi guys, I Have a question, Is IT possible to make Custom kernel looks like Stock. I mean that phone Will not write on boot screen KERNEL IS NOT SEADROID ENFORCING and CHECK WARRANTY BIT: KERNEL. Thanks for your advices and sorry for my english.