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
Related
I was trying to root my S4 using the video and downloads provided by QBking77. That did not work so I tried to update Samsung software.
I got a message saying the software has been downloaded and will be installed. Clicked yes and now all I get is a black screen with recover booting on the upper left hand side corner.
Please help.
Go do some research on Odin. I'm not very knowledgeable in this, I came from HTC, but I think Odin can help you.
Sent from my SPH-L720 using Tapatalk 2
Sphansek said:
I was trying to root my S4 using the video and downloads provided by QBking77. That did not work so I tried to update Samsung software.
I got a message saying the software has been downloaded and will be installed. Clicked yes and now all I get is a black screen with recover booting on the upper left hand side corner.
Please help.
Click to expand...
Click to collapse
First try pulling the battery and starting again. If you are still stuck you are going to want to Odin the stock tar back on.
Sent from my SPH-L720 using xda premium
crawrj said:
First try pulling the battery and starting again. If you are still stuck you are going to want to Odin the stock tar back on.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Thanks for the quick replies guys. I dunno what I did but somehow its working again. Pulled out the battery and still the screen with Samsung Galaxy S4 and recovery booting showing on the screen. Pressed the power off + volume down + home screen button and was somehow able to restart the phone which seems to be working fine now.
The problem is I dont know what happened there? And if its safe to go ahead and update the samsung software or not?
Any clue? Any advice is appreciated.
Sounds like a typical update fail to me. It will most likely do the same thing if you try again.
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.
Anyone else having problems using wanam exposed to get rid of the custom unlock when booting up? It doesn't change in about phone either. It does say "official" in about phone though. It doesn't seem like the hack is working at all
You need to reboot twice to see it in effect. First reboot will still sees lock. 2nd reboot and in it will be gone.
Sent from my GlaDos Baked Potato
After the mj7 update you night have an issue with it not working on my stock rooted rom gone but on my hyper drive and beans rim slots it has issues going away after using wanam
Sent from my SM-N900V using Tapatalk
After countless reboots, simple fix was using triangle away app from playstore.
Sent from my SM-N900V using Tapatalk
use triangle away i am on mj7 and used it no custom boot any longer
saint365 said:
After countless reboots, simple fix was using triangle away app from playstore.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Thank you! Triangle away did the trick!
anthony92170 said:
use triangle away i am on mj7 and used it no custom boot any longer
Click to expand...
Click to collapse
Thank you! Triangle away did the trick!
TA ... which setting worked?
Beeing a bit of a noob, and not wanting to brick my phone by clicking the wrong option in "Triangle Away" ... exactly which setting did you select to remove the "custom" from the boot screen on the Note 3?
Thanks, in advance, for your help!
drtrask said:
Beeing a bit of a noob, and not wanting to brick my phone by clicking the wrong option in "Triangle Away" ... exactly which setting did you select to remove the "custom" from the boot screen on the Note 3?
Thanks, in advance, for your help!
Click to expand...
Click to collapse
Reset flash counter.
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
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 ...