So during my last root/TWRP/xposed install, I started seeing "Kernel is not seandroid enforcing" when I boot. When I've googled around, this usually means I shouldn't be able to boot up, however I boot up just fine. Am I fine to just leave it as it is, as it doesn't seem to be causing any issues. Or are there problems with keeping the kernel in this state. Thanks!
I also have this on my S5 right after I flashed a custom rom yesterday.
The phone seems to work fine but this seems a bit off so I was wondering why this is showing up at the bootup ?
re: seanroid
shogun168 said:
So during my last root/TWRP/xposed install, I started seeing "Kernel is not seandroid enforcing" when I boot. When I've googled around, this usually means I shouldn't be able to boot up, however I boot up just fine. Am I fine to just leave it as it is, as it doesn't seem to be causing any issues. Or are there problems with keeping the kernel in this state. Thanks!
Click to expand...
Click to collapse
darkfart1 said:
I also have this on my S5 right after I flashed a custom rom yesterday.
The phone seems to work fine but this seems a bit off so I was wondering why this is showing up at the bootup ?
Click to expand...
Click to collapse
Everyone gets the "Kernel is not seandroid enforcing" after
rooting and twrping, it's perfectly normal... No worries!.
Have a great day!
Misterjunky said:
Everyone gets the "Kernel is not seandroid enforcing" after
rooting and twrping, it's perfectly normal... No worries!.
Have a great day!
Click to expand...
Click to collapse
Ah, that's a relief. Odd that the first time I rooted and everything, I never got the text. Only popped up after a factory reset and re-root. Anyway, glad to know it's nothing to be concerned about.
Wrong! It is definitely not showing on mine.
krico said:
Wrong! It is definitely not showing on mine.
Click to expand...
Click to collapse
And it didn't before when I rooted my phone .... but I've had this running for a few days and not run into any issues so far. So who knows ...
re: seandroid
krico said:
Wrong! It is definitely not showing on mine.
Click to expand...
Click to collapse
If it's not showing on your phone it means that
your phone is is not twrp'ed and rooted.
Good luck,
Have a great day!
Lol, if my phone wasn't twrp'ed and rooted, then i wouldn't have even bothered to post my comment.
Mine, it just show on the first boot after rooting the phone, after that no more.
Sent from my SM-G935F (Galaxy S7edge)
Misterjunky said:
If it's not showing on your phone it means that
your phone is is not twrp'ed and rooted.
Good luck,
Have a great day!
Click to expand...
Click to collapse
krico said:
Lol, if my phone wasn't twrp'ed and rooted, then i wouldn't have even bothered to post my comment.
Click to expand...
Click to collapse
I've had both cases .. I never had this message before my reset and I was TWRP and rooted. And I've had it post reset, and I still have TWRP and I'm rooted. Odd ...
Related
I recently rooted my phone just to install an app to let me log some issues I'm having with my phone and unfortunately I can't find the problem. I'm going to send in my galaxy S4 to be repaired by Samsung but I want to ensure that they don't know that I rooted my phone. I unrooted the phone using odin and flashed the stock firmware to the phone. In the phone's settings it says "Official" for device status and when I boot the phone into download mode the Current Binary Says: "Samsung Official" and the System Status says "Official". The unrooting guide I used advised me to use Triangle Away to reset the flash counter. However, even when the phone was rooted, the current binary said "Samsung Official" so I decided to go ahead and unroot it without resetting the flash counter. I never flashed a custom rom to the phone. The only thing I did was root it. So, since the current binary said "Samsung Official" before and after unrooting the phone, am I ok to send it in? I'd rather not root the phone again just to reset the counter when it already says "Samsung Official".
Nor did I install a custom recovery.
Anyone?
theloneranger08 said:
Anyone?
Click to expand...
Click to collapse
Factory reset and you should be good
tyshemi said:
Factory reset and you should be good
Click to expand...
Click to collapse
Do I need to do a factory reset even if it already says "Samsung Official". I thought that the only time you need to do a factory reset is if your phone gets stuck in a boot loop.
Lol I would before you send it back but you did the steps correctly so your good either way
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
tyshemi said:
Lol I would before you send it back but you did the steps correctly so your good either way
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
What I'm confused about is that Motochopper is supposed to trip the flash counter but it didn't or at least it didn't appear that it did...
It shouldn't change the binary counter should have just changed the Samsung status is all only flashing Roms that aren't stock from ATT or Samsung should increase binary! If you boot into boot loader does it say official and if so your golden brah
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
tyshemi said:
It shouldn't change the binary counter should have just changed the Samsung status is all only flashing Roms that aren't stock from ATT or Samsung should increase binary! If you boot into boot loader does it say official and if so your golden brah
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
By boot loader do you mean download mode because the recovery mode doesn't say anything? In download mode it says "Samsung Official" for current binary.
theloneranger08 said:
By boot loader do you mean download mode because the recovery mode doesn't say anything? In download mode it says "Samsung Official" for current binary.
Click to expand...
Click to collapse
Lol yea that's what i ment too many phones you should be good to go :cyclops:
Don't get your undies all in a bunch. You're good to go if it all says official.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
tyshemi said:
Lol yea that's what i ment too many phones you should be good to go :cyclops:
Click to expand...
Click to collapse
Ok and you are sure about motochopper not triggering the counter? Apparently, the Galaxy S4 doesn't show the flash counter in download mode, and only shows the current binary. Is it possible for the current binary to say "samsung official" but that flash counter to be 1? Of course, I could reroot, install Triangle Away and it would show me the flash counter, but I'd rather not go through all of that again if I don't have to...
theloneranger08 said:
Ok and you are sure about motochopper not triggering the counter? Apparently, the Galaxy S4 doesn't show the flash counter in download mode, and only shows the current binary. Is it possible for the current binary to say "samsung official" but that flash counter to be 1? Of course, I could reroot, install Triangle Away and it would show me the flash counter, but I'd rather not go through all of that again if I don't have to...
Click to expand...
Click to collapse
Buddy in my opinion I'd say your gtg :laugh::laugh:
tyshemi said:
Buddy in my opinion I'd say your gtg :laugh::laugh:
Click to expand...
Click to collapse
haha ok thanks. I was a little paranoid so I actually ended up rerooting my phone, installing Triangle Away and just like you said, Triangle Away said the flash counter was 0 and the current binary said "Samsung Official" so I unrooted my phone and now I'm good to go. Now I've got peace of mind though. haha
theloneranger08 said:
haha ok thanks. I was a little paranoid so I actually ended up rerooting my phone, installing Triangle Away and just like you said, Triangle Away said the flash counter was 0 and the current binary said "Samsung Official" so I unrooted my phone and now I'm good to go. Now I've got peace of mind though. haha
Click to expand...
Click to collapse
It's better to have a piece of mind lol but I was 99.999999% sure you were fine but anyhow glad your good :good:
tyshemi said:
It's better to have a piece of mind lol but I was 99.999999% sure you were fine but anyhow glad your good :good:
Click to expand...
Click to collapse
Also, for some odd reason, the superuser app was still there when I unrooted. Of course it no longer worked and I promptly uninstalled it. I've read that it will sometimes come back if the phone is reset though...
theloneranger08 said:
Also, for some odd reason, the superuser app was still there when I unrooted. Of course it no longer worked and I promptly uninstalled it. I've read that it will sometimes come back if the phone is reset though...
Click to expand...
Click to collapse
Make sure you use full unroot in the super user then uninstall from play store then reboot and see!
tyshemi said:
Make sure you use full unroot in the super user then uninstall from play store then reboot and see!
Click to expand...
Click to collapse
I didn't unroot using the superuser. I put the phone in download mode and flashed stock firmware to it.
theloneranger08 said:
I didn't unroot using the superuser. I put the phone in download mode and flashed stock firmware to it.
Click to expand...
Click to collapse
Your good buddy leave it be now and relax its a done deal good efforts on solidifying the stock state
tyshemi said:
Your good buddy leave it be now and relax its a done deal good efforts on solidifying the stock state
Click to expand...
Click to collapse
haha alright I appreciate the help.
I tried to use GooManager to install TWRP, and now every time I try to reboot, the phone gets to the "Samsung Galaxy Note 3" page with three lines at the top - they say:
Recovery booting.....
Recovery is not seandroid enforcing
Set Warrant Bit : Recovery
I was on the leaked KitKat firmware. Can I fix this without losing everything? Or should I just restore the 4.4 using ODIN and re-root?
ManUtdRul3 said:
I tried to use GooManager to install TWRP, and now every time I try to reboot, the phone gets to the "Samsung Galaxy Note 3" page with three lines at the top - they say:
Recovery booting.....
Recovery is not seandroid enforcing
Set Warrant Bit : Recovery
I was on the leaked KitKat firmware. Can I fix this without losing everything? Or should I just restore the 4.4 using ODIN and re-root?
Click to expand...
Click to collapse
I read one post that says TWRP hasn't been updated yet to run kitkat. Try CWM.
hey_joe said:
I read one post that says TWRP hasn't been updated yet to run kitkat. Try CWM.
Click to expand...
Click to collapse
I've managed to completely restore my phone. Just need to re-root now; can you provide a link to the up to date CWM?
ManUtdRul3 said:
I've managed to completely restore my phone. Just need to re-root now; can you provide a link to the up to date CWM?
Click to expand...
Click to collapse
Here you go
hey_joe said:
Here you go
Click to expand...
Click to collapse
You're awesome, thank you!
hey_joe said:
Here you go
Click to expand...
Click to collapse
I've just got one more question.
I can root using this right? https://plus.google.com/+Chainfire/posts/QbVy3arpymx
I did this a few days and it worked fine. When I went to do it again earlier it ****ed up and let to that error again.
That's when I restored everything again and asked you for CWM.
Someone on there (third from bottom) mentioned they had the same error.
ManUtdRul3 said:
I've just got one more question.
I can root using this right? https://plus.google.com/+Chainfire/posts/QbVy3arpymx
I did this a few days and it worked fine. When I went to do it again earlier it ****ed up and let to that error again.
That's when I restored everything again and asked you for CWM.
Someone on there (third from bottom) mentioned they had the same error.
Click to expand...
Click to collapse
Yup use CF Here - should work spot on
radicalisto said:
Yup use CF Here - should work spot on
Click to expand...
Click to collapse
Thanks. Any idea why it came up with that other error/problem/bootloop?
ManUtdRul3 said:
Thanks. Any idea why it came up with that other error/problem/bootloop?
Click to expand...
Click to collapse
It seems it does it every now and again for whatever reason, I was lucky my root worked right away but my flashing of 4.4.2 didn't lol -- Reflash 4.4.2 via Odin then re-root. Should be good to go mate
EDIT: Careful if you are restoring anything via CWM, as it has just been done for 4.4.2 there *may* be issues with it that haven't been noticed.
radicalisto said:
It seems it does it every now and again for whatever reason, I was lucky my root worked right away but my flashing of 4.4.2 didn't lol -- Reflash 4.4.2 via Odin then re-root. Should be good to go mate
Click to expand...
Click to collapse
I just used that root and it happened again?
It's bootlooping again?
radicalisto said:
It's bootlooping again?
Click to expand...
Click to collapse
Yeah :/ I'm so confused, this worked the first time I rooted KitKat
ManUtdRul3 said:
Yeah :/ I'm so confused, this worked the first time I rooted KitKat
Click to expand...
Click to collapse
OK, so you'll defo have to reflash from scratch, then boot her up and set up, then re-root - try not to restore anything.
radicalisto said:
OK, so you'll defo have to reflash from scratch, then boot her up and set up, then re-root - try not to restore anything.
Click to expand...
Click to collapse
When you say don't restore anything, you mean that automatic restore from Google?
ManUtdRul3 said:
When you say don't restore anything, you mean that automatic restore from Google?
Click to expand...
Click to collapse
Yeah, try and root it on very basic system just too see, it might not be playing too well with things as it stands
radicalisto said:
Yeah, try and root it on very basic system just too see, it might not be playing too well with things as it stands
Click to expand...
Click to collapse
Hmm okay. Just a piss take how I'll have to keep re-installing all the things I need!
Yup it's a proper ballache for sure, been there myself many many times and prepared to be there again a few times yet lol
radicalisto said:
Yeah, try and root it on very basic system just too see, it might not be playing too well with things as it stands
Click to expand...
Click to collapse
Reflashed stock ROM, rooted without restoring anything and it's happened again...
ManUtdRul3 said:
Reflashed stock ROM, rooted without restoring anything and it's happened again...
Click to expand...
Click to collapse
OK Your phone HATES you lol,
Last thing I can think of, is you may have had the wrong file try This one at the bottom of the page is the link. If you already have this one, then Re-flash Stock to fix yourself, and hold tight on root until it can be figured out 100% for now.
radicalisto said:
OK Your phone HATES you lol,
Last thing I can think of, is you may have had the wrong file try This one at the bottom of the page is the link. If you already have this one, then Re-flash Stock to fix yourself, and hold tight on root until it can be figured out 100% for now.
Click to expand...
Click to collapse
Yeah that's the one I had :/ This is horrible haha
Now I regret messing around this morning at college, using GooManager while I should have been studying...
I just want root back so I can install Xposed, Greenify and Titanium Backup to freeze the bloat
Hello, I'm trying to root my note 3 and every time i just get a blue red yellow text that says "RECOVERY BOOTING..... RECOVERY IS NOT SEANDROID ENFROCING Set warranty Bit: recovery." Eventually I can manage to get outside of this error but the phone still isn't rooted, it's a N9005 running on 4.3
Axel the Inferno said:
Hello, I'm trying to root my note 3 and every time i just get a blue red yellow text that says "RECOVERY BOOTING..... RECOVERY IS NOT SEANDROID ENFROCING Set warranty Bit: recovery." Eventually I can manage to get outside of this error but the phone still isn't rooted, it's a N9005 running on 4.3
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2522858
antiguangenius said:
http://forum.xda-developers.com/showthread.php?t=2522858
Click to expand...
Click to collapse
Thanks, I followed the guide and got root on now, but I've noticed a new problem. The mm-qcamera-daemon process is always running and really chews through battery life. Any ideas how to stop it from running unless I use Camera, which currently I can't even use because the process for camera control is being used by unknown sources. Also I do not have any apps that use the camera, other than Camera.
Greenify the camera maybe
Sent from my SM-N9005 using XDA Premium 4 mobile app
I have recently tried to unroot my Galaxy S4 T Mobile phone with no success. I have ClockworkMod Recovery on it. When I connect my phone in the boot loader screen it wont connect to my computer. When I try and boot up the phone it just boots up to the Galaxy S4 Screen and stops and does not do anything. It reads in the top left head corner "KEANEL IS NOT SEANDROID ENFOACING Set Warranty Bit: kernel" If someone can guide me in the right direction any help will be greatly appreciated.
Frankenstien3 said:
I have recently tried to unroot my Galaxy S4 T Mobile phone with no success. I have ClockworkMod Recovery on it. When I connect my phone in the boot loader screen it wont connect to my computer. When I try and boot up the phone it just boots up to the Galaxy S4 Screen and stops and does not do anything. It reads in the top left head corner "KEANEL IS NOT SEANDROID ENFOACING Set Warranty Bit: kernel" If someone can guide me in the right direction any help will be greatly appreciated.
Click to expand...
Click to collapse
May be kernel corrupted ! Jus flash stock s4 rom using odin...you'll be okay then
Always take a nandroid backup
Before any modifications, ths includes rooting too
Sent from my Nokia_XL using XDA Premium 4 mobile app
Just flash stock rom true Odin.
Frankenstien3 said:
I have recently tried to unroot my Galaxy S4 T Mobile phone with no success. I have ClockworkMod Recovery on it. When I connect my phone in the boot loader screen it wont connect to my computer. When I try and boot up the phone it just boots up to the Galaxy S4 Screen and stops and does not do anything. It reads in the top left head corner "KEANEL IS NOT SEANDROID ENFOACING Set Warranty Bit: kernel" If someone can guide me in the right direction any help will be greatly appreciated.
Click to expand...
Click to collapse
Your Knox counter is tripped. You cannot fix this.
You can unroot it.
You can take the custom recovery off of it and put the stock one back.
You can revert to full stock everything.
But the Knox counter is still going to be tripped and its' still going to say "Kernel in not seandroid enforcing"
Skipjacks said:
Your Knox counter is tripped. You cannot fix this.
You can unroot it.
You can take the custom recovery off of it and put the stock one back.
You can revert to full stock everything.
But the Knox counter is still going to be tripped and its' still going to say "Kernel in not seandroid enforcing"
Click to expand...
Click to collapse
I always thought that you get that message when you run a custom kernel that has seandroid disabled. Doesn't the message disappear when you flash a stock kernel?
Lennyz1988 said:
I always thought that you get that message when you run a custom kernel that has seandroid disabled. Doesn't the message disappear when you flash a stock kernel?
Click to expand...
Click to collapse
It wil disappear after flashing stock. I mean fully stock including recovery, boot, firmware
Sent from my Nokia_XL using XDA Premium 4 mobile app
my device suffers of random reboots during the day. it happens more than once a day and this doesn't depend from how much time i use it. this reboots are completly unexpected. how i can resolve this ?
you need to provide more detail here. Did you root your tablet and then started random reboot?
jazzespresso said:
you need to provide more detail here. Did you root your tablet and then started random reboot?
Click to expand...
Click to collapse
i never rooted my device and i restored it by using samsung SmartSwtich(kies) 2 times.
catchtheball said:
i never rooted my device and i restored it by using samsung SmartSwtich(kies) 2 times.
Click to expand...
Click to collapse
if you never rooted and if your device untouched not alerted and still under factory warranty, then I would suggest you to return it or exchange it...
jazzespresso said:
if you never rooted and if your device untouched not alerted and still under factory warranty, then I would suggest you to return it or exchange it...
Click to expand...
Click to collapse
ok. but if i try to root it i will invalid the warranty ?
catchtheball said:
ok. but if i try to root it i will invalid the warranty ?
Click to expand...
Click to collapse
yes