How do I get rid of the message 'the kernel is not seandroid enforcing ' when my Tab S2 boots up. It's running on V5.1.1 Build Number T810XXU2BOJ1.
The TabS2 is rooted and has TWRP Recovery installed.
Thanks
Normal when using a custom kernel.
schrodinger56 said:
How do I get rid of the message 'the kernel is not seandroid enforcing ' when my Tab S2 boots up. It's running on V5.1.1 Build Number T810XXU2BOJ1.
The TabS2 is rooted and has TWRP Recovery installed.
Thanks
Click to expand...
Click to collapse
You can't. Nothing wrong operational all it is saying is that you're rooted.
Related
CWM Manager should be used with CF-Root V5.0 or newer it appears you are running a different kernel.various features have been disabled problem
i have problem in my Galaxy Tab p1000
picture in attachment
any one can help me to update kernel?
thanks in advanced
no solution, but the same Problem.
Having an P1010 with Gingerbread an CF-Root.
bedoo54 said:
CWM Manager should be used with CF-Root V5.0 or newer it appears you are running a different kernel.various features have been disabled problem
i have problem in my Galaxy Tab p1000
picture in attachment
any one can help me to update kernel?
thanks in advanced
Click to expand...
Click to collapse
This happens when CWM does not have necessary root access. Maybe you reflashed the stock kernel after installed insecure kernel to remove the yellow triangle. If that is the case simply reflash with insecure kernel and start CWM after phone boots. Allow it superuser access and go to CWM Recovery mode from the app.
Let me know if you are stuck somewhere. I had the same issue as yours 5 minutes back and found a way myself. Hope this helps. I just flashed a custom XXLP6 for my SGS2.
hi!
can i ask sth?
if the message like this..
"CWM Manager should be used with CF-Root V5.0 or newer it appears you are running a different recovery.various features have been disabled problem"
yea, i know that after i install the latest cf-root with cwm including on,
then i install touch cwm on my phone, it'll response that..
so my questions :
1. is that touch cwm is just can be access from boot recovery?;
2. can i get back the feature that has been disabled to be enabled again?
3. lastly, can i just uninstall cwm, and is that touch cwm and cwm manager still installed on?
Just uninstal the app. With root explorer.
Sent from my GT-S5300 using Tapatalk 2
Hi everyone. I was running Omni Rom 4.4.2 on my Note when I saw the developers team release the new kernel with addition governors. I downloaded it and flash it in the recovery but I accidentally hit the "reboot system" instead of "reboot recovery". Now my phone is stuck in Samsung Logo, and I can't enter recovery What should I do now? Should I try to flash PhilZ Kernel (the TW only newest version) through Odin to be able to get into recovery ? Or should I do something else ? I have never used Odin before Please kindly help me
yeah use Philz odin version of kernel, then boot into recovery and reflash the rom again.
I don't know what happened, the Note I, first had Philz recovery, then I flashed the kernal & asylum Rom as per instruction, got some error, so I reboot, then I got CWM, flash again, reboot, didn't work, hold three buttons got into recovery now it's TWRP 2.7? ? Didn't know 2.7 is even available for the Note I. What is going on?
I think 2.7 is not available for the Note now.
But I have TWRP on the Note I N7000
kuromusha38 said:
But I have TWRP on the Note I N7000
Click to expand...
Click to collapse
It's because the asylum rom u flashed has TWRP recovery built in. When you flashed it, the TWRP override your CWM.
kuromusha38 said:
I don't know what happened, the Note I, first had Philz recovery, then I flashed the kernal & asylum Rom as per instruction, got some error, so I reboot, then I got CWM, flash again, reboot, didn't work, hold three buttons got into recovery now it's TWRP 2.7? ? Didn't know 2.7 is even available for the Note I. What is going on?
Click to expand...
Click to collapse
The kernel you flashed had CWM. The PhilZ version you had probably didn't have SELinux support, so it couldn't flash Asylum ROM. You rebooted recovery, it loaded the recovery from the kernel you flashed. Whatever the kernel was, it had SELinux support, so you were able to flash Asylum ROM. Asylum ROM uses TWRP, so when you booted into recovery, you had TWRP. And yes there is TWRP 2.7.0.0 for our Note. Not strange at all
Ok ,
I tried to extend the lifetime of my Galaxy Note through replacing the official (sloooow) rom with a custom one. I read so many how-to's online that I got confused. Here is what I did:
First I rooted my phone.
Then I installed CWM via RomManager, which did not work. Altough Rommanager shows an installed CWM the phone always start into Stock Recovery.
I learned that the N7000, in order to use CWM needs a flashed kernel.
I flashed the kernel via Heimdall (Mac OS) with this philz_touch_6.48.4-n7000.tar.md5.
The flashing went successfull (according to Heimdall), and the phone rebooted automatically, but all I see since then is the Samsung Logo (Samsung Galaxy Note GT-N7000) and a yellow triangle. From there is goes nowhere. I can enter Download Mode, but is does not boot. Also no Recovery Mode. Weird.
Any advice where to take it from here? Do I have to flash back the original kernel?
Try an older philz. That one you used is to new gor Stock Samsung Rom. What rom is currently installed?
grosserzampano said:
Ok ,
I tried to extend the lifetime of my Galaxy Note through replacing the official (sloooow) rom with a custom one. I read so many how-to's online that I got confused. Here is what I did:
First I rooted my phone.
Then I installed CWM via RomManager, which did not work. Altough Rommanager shows an installed CWM the phone always start into Stock Recovery.
I learned that the N7000, in order to use CWM needs a flashed kernel.
I flashed the kernel via Heimdall (Mac OS) with this philz_touch_6.48.4-n7000.tar.md5.
The flashing went successfull (according to Heimdall), and the phone rebooted automatically, but all I see since then is the Samsung Logo (Samsung Galaxy Note GT-N7000) and a yellow triangle. From there is goes nowhere. I can enter Download Mode, but is does not boot. Also no Recovery Mode. Weird.
Any advice where to take it from here? Do I have to flash back the original kernel?
Click to expand...
Click to collapse
The phone doesn't boot because the kernel you flashed is a kitkat kernel.
You should have recovery mode. Try to remove the battery for couple of seconds and then try to get into recovery. If still no go..
Go to Philz thread and look for tw kernels link. Go there and flash XXLTA kernel using odin. Now try recovery mode again.
User_99 said:
Try an older philz. That one you used is to new gor Stock Samsung Rom. What rom is currently installed?
Click to expand...
Click to collapse
I have the Stock Samsung Android 4.1.2 installed. I'll try it again with an older kernel. Thanks for your help.
nokiamodeln91 said:
The phone doesn't boot because the kernel you flashed is a kitkat kernel.
You should have recovery mode. Try to remove the battery for couple of seconds and then try to get into recovery. If still no go..
Go to Philz thread and look for tw kernels link. Go there and flash XXLTA kernel using odin. Now try recovery mode again.
Click to expand...
Click to collapse
I tried it several times, also after removing the battery. no success. Is is necessary to use ODIN? I use Heimdall as I mentioned, because I am running Mac OS.
I'll try it with a different kernel and report back here about my results. Thanks a lot.
Thanks for your help. I searched through that Philz Thread and found the link to the older kernels. Then I picked this version after asking google for a compatible kernel with N7000 Samsung Rom Android 4.1.2.
Kernel PhilZ-cwm6-XXLTA-ATL-5.15.0
I flashed it with Heimdall and finally the device boots again. Still not able to boot into Clockworkmod. Device does not enter Recovery mode at all. But at least I have a working device for now again.
What
grosserzampano said:
Thanks for your help. I searched through that Philz Thread and found the link to the older kernels. Then I picked this version after asking google for a compatible kernel with N7000 Samsung Rom Android 4.1.2.
Kernel PhilZ-cwm6-XXLTA-ATL-5.15.0
I flashed it with Heimdall and finally the device boots again. Still not able to boot into Clockworkmod. Device does not enter Recovery mode at all. But at least I have a working device for now again.
Click to expand...
Click to collapse
Install terminal emulator and try the command
su
reboot recovery.
Now that is weird. After the device booted again I seemed to lost root access to the device. I tried to get root again with Framaroot, also installed SuperUser again since it was magically deinstalled. Now the device booted into the logo with the yellow triangle and then the screen turned black. Nothing happened from there.
Fortunately I had the idea to use adb on the device before trying to flash an original Samsung Rom back on the device out of pure despair. adb listed the device and stated that the device is in recovery mode. It seems that the device always booted into recovery, altough I tried to boot normally. Recovery still not working. But using "adb reboot" helped to reboot the device again.
Trying to start in recovery mode, i.e. with adb reboot recovery always ends up in a black screen. Somehow this is broken.
I think I have to go back to zero and try to follow a good guide from the beginning without mixing several guides.
grosserzampano said:
Now that is weird. After the device booted again I seemed to lost root access to the device. I tried to get root again with Framaroot, also installed SuperUser again since it was magically deinstalled. Now the device booted into the logo with the yellow triangle and then the screen turned black. Nothing happened from there.
Fortunately I had the idea to use adb on the device before trying to flash an original Samsung Rom back on the device out of pure despair. adb listed the device and stated that the device is in recovery mode. It seems that the device always booted into recovery, altough I tried to boot normally. Recovery still not working. But using "adb reboot" helped to reboot the device again.
Trying to start in recovery mode, i.e. with adb reboot recovery always ends up in a black screen. Somehow this is broken.
I think I have to go back to zero and try to follow a good guide from the beginning without mixing several guides.
Click to expand...
Click to collapse
May be the recovery partition is messed up due to the usage of rom manager earlier. Try to flash a stock rom.
grosserzampano said:
Ok ,
I tried to extend the lifetime of my Galaxy Note through replacing the official (sloooow) rom with a custom one. I read so many how-to's online that I got confused. Here is what I did:
First I rooted my phone.
Then I installed CWM via RomManager, which did not work. Altough Rommanager shows an installed CWM the phone always start into Stock Recovery.
I learned that the N7000, in order to use CWM needs a flashed kernel.
I flashed the kernel via Heimdall (Mac OS) with this philz_touch_6.48.4-n7000.tar.md5.
The flashing went successfull (according to Heimdall), and the phone rebooted automatically, but all I see since then is the Samsung Logo (Samsung Galaxy Note GT-N7000) and a yellow triangle. From there is goes nowhere. I can enter Download Mode, but is does not boot. Also no Recovery Mode. Weird.
Any advice where to take it from here? Do I have to flash back the original kernel?
Click to expand...
Click to collapse
go to download mode and flash stock rom of note 1 via odin then after successful installation u can go to recovery mode and install this zip ur phone will be rooted and phliz touch will be installed
for any help u can PM me
Hi all
I'm stuck with this error message.
I installed twrp. Then flashed the latest cm13 nightly. Im' not able to boot as I get a red error message saying "kernel is not seandroid enforcing"
Note that if I flash superSU, this fu**ing message doesn't show up any more but I get a bootloop instead....
Help please.
Thanks in advance
Wipe your data partition.
Cm13 wont be compatible with your existing TouchWiz data.
Thanks.
Data partition formated. Cm13 flashed again..... And the "kernel is not seandroid enforcing" message comes again......
prius77 said:
Thanks.
Data partition formated. Cm13 flashed again..... And the "kernel is not seandroid enforcing" message comes again......
Click to expand...
Click to collapse
The message is irrelevant and means nothing. It wont prevent it from booting.
I suggest you post in the relevant thread if there is an issue with the kernel or rom.
Ok.. Will try to reinstall the stock Samsung Rom and reinstall custom recovery/rom via Odin.