I can't charge my phone offline when i turn it off, when i try it, then it says "Kernel is not seandroid enforcing" and then it reboots. by charging online i broke my battery life by 50% even in airplane mode, please help or send some fixes, I tried some but they didn't work. :crying:
UPDATE : I flashed CyanogenMod 12.1 Unofficial which has android 5.1.1, so if there are no answers for it then my question would be : how to remove that "kernel (or recovery) is not seandroid enforcing" (there's no "set warranty bit" message), can I bypass it somehow?
UPDATE 2 : I removed "kernel is not seandroid enforcing" by installing the latest kernel which supports cm12.1 s3ve3g
I'm active and I need the first question, I didn't solve it
If you don't know sir
offline charging is a bug in cm12.1 bug so you won't be able to charge it offline
try @n1kolaa kernel i think it has offline charging working
Related
Hello,
I know there are a lot of topics about the "Kernel is not seandroid enforcing". But my I9505 shows that message, but is stuck at that screen. It only vibrates randomly when turned on.
Today i rooted my device, then i installed CWM, and then i tried to install a new ROM (Google rom). One of those ones must have caused it.
When i try to start recovery mode or download mode, it works 1 in a 100 times. I've tried to wipe all data but nothing helps...
Does anyone know what to do now?
I found a solution to make it work again! I just tried a 100 times to open the download mode. Once i had it i installed this stock rom using Odin:
http://forum.xda-developers.com/showthread.php?t=2250824
That worked for me!
[Q] Flashed kernel, get "seandroid enforcing", now nandroid not working, please help
I tried flashing arter97 kernel for Galaxy Note 3 on my International N9005 running N9005XXUGBOA5 Echoe Rom v.23 which I understand uses the AEL kernel. I'm now getting "KERNEL IS NOT SEANDROID ENFORCING, Set warranty bit: kernel" message and it doesn't boot, just stuck on N9005 screen. Read the kernel OP a few times and searched the thread but can't find a solution, did I miss something?
Then tried to restore my nandroid backup but it gets stuck on the Samsung logo, tried the N3 AEL Kernel v1 but get the SEANDROID message and no boot again, can someone please point me in the right direction as it's been a while since I've done this?
Well, this is the weirdest but simple fix to this bizarre problem, after nearly a full day struggling to get the phone to boot, even flashing a stock ROM with Odin I found an obscure post on a thread here on XDA which fixed it. The trick was to boot into download mode and then on the screen that shows 'up volume' to continue and 'down volume' to cancel, press 'down volume' to cancel and then the phone booted, that's it! How utterly odd!
dear friends kindly help:
i am flash custom rom ( N910G_OH4_N5P_DrKetan_ROM_L12 )
after flashing
phone display following message when startup
kernel is not seandroid enforcing
set warranty bit : kernel
then appear samsung logo for 1 minut then phone restart
what i can do ;;;;;;
suggest me please
Hi all :angel:
after several attempt finally i got CM 13 on my G900F everything looks great except :
The phone is rebooting some times and i have this message on the boot "kernel is not seandroid enforcing set warranty bit kernel"
is that related ?!!
how can i fix this :silly::fingers-crossed:
Boot average ::crying::crying:
In the first 3 hours : every 20-30 minutes
and from 17h to 9h of this morning every thing seems Ok
then the problem is back
what i have use :
- odin v 3.09
- cm-13.0-20160314-NIGHTLY-klte
- open_gapps-arm-6.0-stock-20160315
- twrp-3.0.0-0-klte-klte.img
PS : sorry for my english
The message on the boot is normal for everyone,the reboots might be from some apps that don't agree with the system so it force reboots to fix itself.
I have everything the same as you and I don't see any problems.
Hi, I recently rooted my Galaxy S7 edge (G935W8) and everything works but whenever I reboot my phone it says Kernel is not Seandroid Enforcing in red on the top left corner. I did a bit of research and apparently people who have encountered this issue are not able to boot their phone at all, whereas I can boot it without problem. Any idea why this is happening? Is it indicative of some sort of system error?
Thanks.