phone continues reboot after samsung logo : note 4 smn-910g - Galaxy Note 4 Q&A, Help & Troubleshooting

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

Related

MIUI for note 3 troubleshoot

hi , i just install miui on my note 3 n9005 using cwm recovery it just take 3-4min to install. then i restart phone. i seen a massage on black screen "kernel is not seandroid enforcing" after 10-15sec phone start normally and everything is working fine. i seen the massage on every power on or restart. why this massage showing? is this harmful ? what to do? how can i release from this massage .
please help me
see the attachment of black screen massage

[Q] [HELP] SM-N9005 bootloop bobcatrom, not entering download/recovery mode

Hi there
having an unlocked SM-N9005, flashed custom ROM (Bobcat) some months back, returned to stock-rom yesterday, all went fine. Decided then to give Bobcat another try, flashed it with Odin, 'passed'. It then got stuck in a bootloop and when trying to enter in download or recovery mode I got this nice little red message "kernel not seandroid enforcing' and in yellow 'set warranty Bit: kernel'. I know this most likely has to do with the kernel I have chosen when setting up bobcat BUT now I can't flash anything nor can I do a recovery....?
any ideas?
Remove the battery, wait one minute, insert the battery and turn on directly with the VolDown+Home+Power. This should start download mode.
svbarbosa said:
Remove the battery, wait one minute, insert the battery and turn on directly with the VolDown+Home+Power. This should start download mode.
Click to expand...
Click to collapse
thanks a ton - that worked!!

[Q] Sprint Galaxy S5 trapped in RECOVERY BOOTING

Hello all Xda members, I think I need some help with rooting Sprint Galaxy S5 because I am having some problems which makes me very very sick While everybody with this phone root easily I am stuck at the start screen and it does not boot.In this screen It says
This is a 10 day-new phone. Any help would be appreciated.
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
Turn off your phone and remove the battery for 30 or so seconds. Then try bootting it up. On first boot ir does take a bit before os comes up. But usually it shows samsung logo.

[CM12.1] [GT-I9301I] Offline charging

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

CM 13 S5 G900F issue

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.

Categories

Resources